From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbox@nvidia.com
Subject: Re: [PATCH v4 0/5] vhost: FD manager improvements
Date: Tue, 11 Jun 2024 16:52:03 +0200 [thread overview]
Message-ID: <CAJFAV8yisT10JUeOhRaPUr2z1tVqkXiargS6pDfRfdyS_PHxPA@mail.gmail.com> (raw)
In-Reply-To: <20240611133957.72032-1-maxime.coquelin@redhat.com>
On Tue, Jun 11, 2024 at 3:40 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
>
> 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.
>
> Changes in v4:
> ==============
> - Remove useless parameter check (Stephen)
> - Error handling in dset_add (Chenbo)
> - Destroy support fixup in even dispatcher (Chenbo)
> - Refactor fdentry insertion/removal
> - Rebased on top of next-virtio/staging
For the series,
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2024-06-11 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 13:39 Maxime Coquelin
2024-06-11 13:39 ` [PATCH v4 1/5] vhost: rename polling mutex Maxime Coquelin
2024-06-11 13:39 ` [PATCH v4 2/5] vhost: make use of FD manager init function Maxime Coquelin
2024-06-11 13:39 ` [PATCH v4 3/5] vhost: hide synchronization within FD manager Maxime Coquelin
2024-06-11 13:39 ` [PATCH v4 4/5] vhost: improve fdset initialization Maxime Coquelin
2024-06-11 13:39 ` [PATCH v4 5/5] vhost: manage FD with epoll Maxime Coquelin
2024-06-11 14:52 ` David Marchand [this message]
2024-06-12 8:41 ` [PATCH v4 0/5] vhost: FD manager improvements 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=CAJFAV8yisT10JUeOhRaPUr2z1tVqkXiargS6pDfRfdyS_PHxPA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
/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).