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

optimize timeout judgement according to different condition #187

Merged
merged 3 commits into from
Feb 7, 2018
Merged

optimize timeout judgement according to different condition #187

merged 3 commits into from
Feb 7, 2018

Commits on Jan 22, 2018

  1. optimize timeout judgement according to different condition 

    Under the condition that "hasToWait && wait_timeout", there is no need to re-calc hasData to judge timeout
because predicate already include the logic. We only need do it if hasToWait && !wait_timeout. This commit
optimize timeout judgement which slightly improve the performance in some conditions

Signed-off-by: jwang <[email protected]>
    @jwang11
    jwang11 committed Jan 22, 2018
    Configuration menu
    Copy the full SHA
    ef574a7 View commit details
    Browse the repository at this point in the history

Commits on Jan 25, 2018

  1. replace cv->wait(lock) with cv->wait(lock, predicate) and simplify ti… 

    …meout logic

Signed-off-by: jwang <[email protected]>
    @jwang11
    jwang11 committed Jan 25, 2018
    Configuration menu
    Copy the full SHA
    08ab218 View commit details
    Browse the repository at this point in the history

Commits on Jan 31, 2018

  1. Improve logic to return TIMEOUT when not hasData && timeout->sec/nsec==0 

    Signed-off-by: jwang <[email protected]>
    @jwang11
    jwang11 committed Jan 31, 2018
    Configuration menu
    Copy the full SHA
    128309e View commit details
    Browse the repository at this point in the history