From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [PATCH v2 0/5] vhost: FD manager improvements
Date: Wed, 3 Apr 2024 11:24:43 +0200 [thread overview]
Message-ID: <20240403092448.1361820-1-maxime.coquelin@redhat.com> (raw)
This series aims at improving the Vhost FD manager.
The fdset internals is hidden from its callers, the
notification/synchronization is made systematic for
every FD add/del operations and finally the code is
reworked to make use of epoll insteal of poll which
reduces the complexity (less locks involved,
synchrnoization no more necessary).
The series has been tested with both Vhost-user/Virtio-user
and with VDUSE.
David Marchand (1):
vhost: manage FD with epoll
Maxime Coquelin (4):
vhost: rename polling mutex
vhost: make use of FD manager init function
vhost: hide synchronization within FD manager
vhost: improve fdset initialization
lib/vhost/fd_man.c | 431 +++++++++++++++-----------------
lib/vhost/fd_man.c.orig | 538 ++++++++++++++++++++++++++++++++++++++++
lib/vhost/fd_man.h | 48 +---
lib/vhost/socket.c | 38 +--
lib/vhost/vduse.c | 52 +---
5 files changed, 762 insertions(+), 345 deletions(-)
create mode 100644 lib/vhost/fd_man.c.orig
--
2.44.0
next reply other threads:[~2024-04-03 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 9:24 Maxime Coquelin [this message]
2024-04-03 9:24 ` [PATCH v2 1/5] vhost: rename polling mutex Maxime Coquelin
2024-04-03 9:24 ` [PATCH v2 2/5] vhost: make use of FD manager init function Maxime Coquelin
2024-04-03 9:24 ` [PATCH v2 3/5] vhost: hide synchronization within FD manager Maxime Coquelin
2024-04-03 9:24 ` [PATCH v2 4/5] vhost: improve fdset initialization Maxime Coquelin
2024-04-03 9:24 ` [PATCH v2 5/5] vhost: manage FD with epoll Maxime Coquelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240403092448.1361820-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).