From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: xieyongji@bytedance.com, jasowang@redhat.com, mst@redhat.com,
david.marchand@redhat.com, lulu@redhat.com
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [PATCH v1 0/2] vduse: add support for networking devices
Date: Tue, 27 Jun 2023 13:36:50 +0200 [thread overview]
Message-ID: <20230627113652.65283-1-maxime.coquelin@redhat.com> (raw)
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.
[1]: https://lore.kernel.org/lkml/CACGkMEtgrxN3PPwsDo4oOsnsSLJfEmBEZ0WvjGRr3whU+QasUg@mail.gmail.com/T/
RFC -> v1 changes:
==================
- Fail device init if it does not support VERSION_1 (Jason)
Maxime Coquelin (2):
vduse: validate block features only with block devices
vduse: enable Virtio-net device type
drivers/vdpa/vdpa_user/vduse_dev.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
--
2.41.0
next reply other threads:[~2023-06-27 11:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 11:36 Maxime Coquelin [this message]
2023-06-27 11:36 ` [PATCH v1 1/2] vduse: validate block features only with block devices Maxime Coquelin
2023-06-28 2:34 ` Jason Wang
2023-07-02 7:49 ` Yongji Xie
2023-06-27 11:36 ` [PATCH v1 2/2] vduse: enable Virtio-net device type Maxime Coquelin
2023-06-28 2:34 ` Jason Wang
2023-07-02 7:50 ` Yongji Xie
2023-07-02 13:37 ` [PATCH v1 0/2] vduse: add support for networking devices Michael S. Tsirkin
2023-07-03 6:44 ` Jason Wang
2023-07-03 7:43 ` Maxime Coquelin
2023-07-03 7:44 ` Jason Wang
2023-07-03 21:45 ` Michael S. Tsirkin
2023-07-04 8:43 ` Maxime Coquelin
2023-07-04 9:59 ` Michael S. Tsirkin
2023-07-04 13:17 ` Maxime Coquelin
2023-08-10 19:02 ` 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=20230627113652.65283-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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®