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
lib/posix-process: Add option to context switch away from clone caller #1303
lib/posix-process: Add option to context switch away from clone caller #1303
Conversation
Note: it is undecided whether we want to prioritize the parent or the children by default. (cc @michpappas) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice addition, looks good to me.
Reviewed-by: Eduard Vintilă eduard.vintila47@gmail.com
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Reviewed-by: Mihnea Firoiu mihneafiroiu0@gmail.com
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mschlumpp just one minor comment below. Regarding ordering: As discussed offline, there isn't a good default in our case so let's leave it as is.
aa15b4c
to
a92bfff
Compare
a92bfff
to
4def7c7
Compare
Some applications are expecting to run on a cooperative scheduler and will naively assume that the new thread will do some progress even if the clone caller does not context-switch by blocking/yielding. Signed-off-by: Marco Schlumpp <marco@unikraft.io>
4def7c7
to
23683db
Compare
Approved-by: Michalis Pappas michalis@unikraft.io |
Some applications are expecting to run on a cooperative scheduler and will naively assume that the new thread will do some progress even if the clone caller does not context-switch by blocking/yielding. Signed-off-by: Marco Schlumpp <marco@unikraft.io> Approved-by: Michalis Pappas <michalis@unikraft.io> Reviewed-by: Eduard Vintilă <eduard.vintila47@gmail.com> Reviewed-by: Mihnea Firoiu <mihneafiroiu0@gmail.com> GitHub-Closes: #1303
Some applications are expecting to run on a cooperative scheduler and will naively assume that the new thread will do some progress even if the clone caller does not context-switch by blocking/yielding.
Prerequisite checklist
checkpatch.uk
on your commit series before opening this PR;Base target
Additional configuration
CONFIG_LIBPOSIX_PROCESS_CLONE_PREFER_CHILD=y
Description of changes