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.

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

wait_or_add_new returning thread_id_type #2495

Closed
wants to merge 3 commits into from

Conversation

sithhell
Copy link
Member

Instead of pushing the newly available work to the pending queues,
wait_or_add_new now returns a newly created thread_data pointer to
be used in the scheduling loop.


if (scheduler.SchedulingPolicy::wait_or_add_new(
num_thread, running, idle_loop_count))
bool running = this_state.load() < state_stopping;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch.

Instead of pushing the newly available work to the pending queues,
wait_or_add_new now returns a newly created thread_data pointer to
be used in the scheduling loop.
@hkaiser
Copy link
Member

hkaiser commented Apr 18, 2017

@sithhell This needs some fixes before it can be merged. Should it still go into the V1.0 release?

@sithhell
Copy link
Member Author

sithhell commented May 9, 2017

Closing as it doesn't show any benefit, makes perfomance worse.

@sithhell sithhell closed this May 9, 2017
@sithhell sithhell deleted the wait_or_add_new_improvement branch May 9, 2017 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants