From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: jasowang@redhat.com
Cc: xuanzhuo@linux.alibaba.com, xieyongji@bytedance.com,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, david.marchand@redhat.com,
lulu@redhat.com, mst@redhat.com
Subject: Re: [PATCH v7 0/3] vduse: add support for networking devices
Date: Thu, 1 Feb 2024 09:34:11 +0100 [thread overview]
Message-ID: <f25f3c31-c793-4743-a587-0e2063dc2d65@redhat.com> (raw)
In-Reply-To: <20240109111025.1320976-1-maxime.coquelin@redhat.com>
Hi Jason,
It looks like all patches got acked by you.
Any blocker to queue the series for next release?
Thanks,
Maxime
On 1/9/24 12:10, Maxime Coquelin wrote:
> This small series enables virtio-net device type in VDUSE.
> With it, basic operation have been tested, both with
> virtio-vdpa and vhost-vdpa using DPDK Vhost library series
> adding VDUSE support using split rings layout (merged in
> DPDK v23.07-rc1).
>
> Control queue support (and so multiqueue) has also been
> tested, but requires a Kernel series from Jason Wang
> relaxing control queue polling [1] to function reliably,
> so while Jason rework is done, a patch is added to fail init
> if control queue feature is requested.(tested also with DPDK
> v23.11).
>
>
> Changes in v7:
> ==============
> - Fail init only if VIRTIO_NET_F_CTRL_VQ is requested.
> - Convert to use BIT_ULL() macro
> - Rebased
>
> Changes in v6:
> ==============
> - Remove SELinux support from the series, will be handled
> in a dedicated one.
> - Require CAP_NET_ADMIN for Net devices creation (Jason).
> - Fail init if control queue features are requested for
> Net device type (Jason).
> - Rebased on latest master.
>
> Changes in v5:
> ==============
> - Move control queue disablement patch before Net
> devices enablement (Jason).
> - Unify operations LSM hooks into a single hook.
> - Rebase on latest master.
>
> Maxime Coquelin (3):
> vduse: validate block features only with block devices
> vduse: Temporarily fail if control queue feature requested
> vduse: enable Virtio-net device type
>
> drivers/vdpa/vdpa_user/vduse_dev.c | 24 ++++++++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2024-02-01 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 11:10 Maxime Coquelin
2024-01-09 11:10 ` [PATCH v7 1/3] vduse: validate block features only with block devices Maxime Coquelin
2024-01-09 11:10 ` [PATCH v7 2/3] vduse: Temporarily fail if control queue feature requested Maxime Coquelin
2024-01-09 11:38 ` Eugenio Perez Martin
2024-01-10 3:20 ` Yongji Xie
2024-01-11 3:10 ` Jason Wang
2024-01-09 11:10 ` [PATCH v7 3/3] vduse: enable Virtio-net device type Maxime Coquelin
2024-01-10 3:27 ` Yongji Xie
2024-02-01 8:34 ` Maxime Coquelin [this message]
2024-02-01 8:40 ` [PATCH v7 0/3] vduse: add support for networking devices Michael S. Tsirkin
2024-02-01 8:42 ` Maxime Coquelin
2024-02-29 10:16 ` Maxime Coquelin
2024-03-19 12:21 ` Michael S. Tsirkin
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=f25f3c31-c793-4743-a587-0e2063dc2d65@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.com \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®