Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

timers: use only a single TimerWrap instance #20555

Closed
wants to merge 5 commits into from
Closed

timers: use only a single TimerWrap instance #20555

wants to merge 5 commits into from

Commits on May 21, 2018

  1. lib: add internal PriorityQueue class

    @apapirovski
    apapirovski committed May 21, 2018
    Configuration menu
    Copy the full SHA
    3449f04 View commit details
    Browse the repository at this point in the history

  2. timers: use only a single TimerWrap instance 

    Hang all timer lists off a single TimerWrap and use the PriorityQueue
to manage expiration priorities. This makes the Timers code clearer,
consumes significantly less resources and improves performance.
    @apapirovski
    apapirovski committed May 21, 2018
    Configuration menu
    Copy the full SHA
    71140ed View commit details
    Browse the repository at this point in the history

  3. fixup: priority queue changes (1st commit)

    @apapirovski
    apapirovski committed May 21, 2018
    Configuration menu
    Copy the full SHA
    c75a6b2 View commit details
    Browse the repository at this point in the history

  4. fixup: timers fixes

    @apapirovski
    apapirovski committed May 21, 2018
    Configuration menu
    Copy the full SHA
    ccd3506 View commit details
    Browse the repository at this point in the history

  5. fixup: include timerwrap hasref test

    @apapirovski
    apapirovski committed May 21, 2018
    Configuration menu
    Copy the full SHA
    5a0f49e View commit details
    Browse the repository at this point in the history