-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Add thread that runs libuv loop continuously #50880
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vchuravy
requested review from
JeffBezanson and
vtjnash
and removed request for
JeffBezanson
August 11, 2023 15:08
vchuravy
reviewed
Aug 11, 2023
vchuravy
reviewed
Aug 11, 2023
vchuravy
reviewed
Aug 11, 2023
This was referenced Aug 14, 2023
vchuravy
reviewed
Aug 15, 2023
xref #35552 |
vchuravy
reviewed
Aug 30, 2023
vchuravy
reviewed
Aug 30, 2023
vchuravy
reviewed
Aug 30, 2023
cafaxo
reviewed
Aug 31, 2023
This was referenced Sep 6, 2023
vchuravy
force-pushed
the
vc/libuv_lock
branch
from
September 7, 2023 21:09
49fc53a
to
0546798
Compare
Co-authored-by: Valentin Churavy <vchuravy@mit.edu>
to handle the scheduling of the IO thread.
Co-authored-by: Lukas Mayrhofer <cafaxo@gmail.com>
vchuravy
force-pushed
the
vc/libuv_lock
branch
from
October 20, 2023 16:54
d6ce79b
to
e2849c6
Compare
gbaraldi
changed the title
Remove in threaded region and add a thread that runs the UV loop
Add thread that runs libuv loop continuously
Feb 7, 2024
@gbaraldi maybe we should split some of the bug fixes out? |
Already merged this, but just waiting to see if Gabriel had any bugfixes here he wanted to land |
don't we still need to turn this on by default? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
io
Involving the I/O subsystem: libuv, read, write, etc.
multithreading
Base.Threads and related functionality
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is slightly speculative, but it fixes #50643 which is a start. But it hasn't been tested under heavy contention of the uv lock.
It also currently uses the normal mutex but we probably need to switch to a lock that has some form of fairness (maybe #50878 )