You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The changes introduced in IoVecBufferMut that allowed implementing readv
support for virtio-net regressed the performance of vsock device. This
is because now, when we create IoVecBufferMut objects we do a bunch (1
memfd_create and 3 mmap) of system calls. virtio-net device avoids the
performance issue because it creates a single IoVecBufferMut and re-uses
it, whereas vsock is creating a new IoVecBufferMut object for every
packet it receives.
We have a fix for this, which essentially creates a single
IoVecBufferMut that reuses for all the incoming vsock packets during a
connection. The problem with the fix is that it makes unit-tests really
unhappy and we need a significant amount of work to fix them.
So, revert the PR to have main in a clean state. We will fix the vsock
issues out-of-band and re-open the PR.
This reverts commits:
- bc0ba43
- 667aba4
- 5d718d4
- 14e6e33
- 1e4c632
from PR #4799
Signed-off-by: Babis Chalios <[email protected]>
0 commit comments