-
Notifications
You must be signed in to change notification settings - Fork 68
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
ThreadOptions
is not fully used while creating new kernel thread
#790
Comments
@jellllly420 Good job on spotting the bug. Could you try to fix it? |
This was referenced May 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is the
aster-nix::thread::kernel_thread::ThreadOptions
.It has fields representing priority and cpu affinity. But when we create new kernel thread in the code below,
we never use this two fields to construct
TaskOptions
, therefore the bound task is always of default configuration.One problem caused by this issue is that all
Worker
s inWORKERPOOL_HIGH_PRI
are of normal priority instead of real-time priority, which is incorrect and can cause starvation in some specific cases.The text was updated successfully, but these errors were encountered: