generated from rust-vmm/crate-template
-
Notifications
You must be signed in to change notification settings - Fork 46
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
vsock: Have two separate threads for handling TX and RX #323
Labels
enhancement
New feature or request
Comments
Thank you for the analysis! If you have time and interest to start this work, go ahead, otherwise we'll do it later because it would be a great cleanup. |
Yes, I'll get to it in a few days. |
This was referenced Oct 24, 2023
Hey i see this hasn't been picked up in quite some time. If no one is picking this up shall i do it? |
@ramyak-mehra great! yes please, go head. IIUC @techiepriyansh is busy, but feel free to ping us if the situation is changed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the
VhostUserVsockBackend
handles both TX and RX in a single thread. It would be nice to have two separate threads handling TX and RX.Implementing this would involve the following:
VhostUserVsockBackend
with the appropriatequeue_mask
s:1
for the RX thread and2
for the TX thread.BACKEND_EVENT
s by callingset_vring_worker
during initialization instart_backend_server
.VhostUserVsockBackend::handle_event
depending on thethread_id
.backend_rxq
contained inVsockThreadBackend
to be accessible by both the threads (maybe over anRwLock
).The text was updated successfully, but these errors were encountered: