Skip to content

fix: Improved thread usage under congestion - #3258

Open
jmachowinski wants to merge 1 commit into
rollingfrom
jm/cbg_perf_improvement
Open

fix: Improved thread usage under congestion#3258
jmachowinski wants to merge 1 commit into
rollingfrom
jm/cbg_perf_improvement

Conversation

@jmachowinski

Copy link
Copy Markdown
Collaborator

Description

Some improvements on thread wakeups

Fixes # (issue)

Is this user-facing behavior change?

no

Did you use Generative AI?

no

Additional Information

Signed-off-by: Janosch Machowinski <J.Machowinski@cellumation.com>

@fujitatomoya fujitatomoya left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

lgtm with minor comment.

Comment on lines +295 to 299
/**
* Will be called while holding the ready_callback_groups_mutex lock
*/
virtual ExecutableEntityWithInfo get_next_ready_entity_intern() = 0;
virtual ExecutableEntityWithInfo get_next_ready_entity_intern(

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

now i do not explain why those virtual methods overload in FirstInFirstOutScheduler are public? before the PR, they were self-locking but now it is caller's responsibility as mentioned. how about moving both pure-virtual declarations into the protected: section (nothing outside the class hierarchy should call them)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants