From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: qemu-devel@nongnu.org,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Andrew Melnychenko <andrew@daynix.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>
Cc: Akihiko Odaki <akihiko.odaki@daynix.com>
Subject: [PATCH RFC v3 00/11] virtio-net: Offload hashing without eBPF
Date: Sun, 15 Sep 2024 10:23:41 +0900 [thread overview]
Message-ID: <20240915-hash-v3-0-79cb08d28647@daynix.com> (raw)
Based-on: <20240915-queue-v1-0-b49bd49b926d@daynix.com>
("[PATCH 0/7] virtio-net fixes")
I'm proposing to add a feature to offload virtio-net RSS/hash report to
Linux. This series contain patches to utilize the proposed Linux feature.
The patches for Linux are available at:
https://lore.kernel.org/r/20240915-rss-v3-0-c630015db082@daynix.com/
This work will be presented at LPC 2024:
https://lpc.events/event/18/contributions/1963/
---
Akihiko Odaki (11):
qdev-properties: DEFINE_PROP_ON_OFF_AUTO_BIT()
net/vhost-vdpa: Report hashing capability
virtio-net: Move virtio_net_get_features() down
virtio-net: Retrieve peer hashing capability
net/vhost-vdpa: Remove dummy SetSteeringEBPF
virtio-net: Add hash type options
net: Allow configuring virtio hashing
virtio-net: Use qemu_set_vnet_hash()
virtio-net: Offload hashing without vhost
tap: Report virtio-net hashing support on Linux
docs/devel/ebpf_rss.rst: Update for peer RSS
docs/devel/ebpf_rss.rst | 23 ++-
include/hw/qdev-properties.h | 18 +++
include/hw/virtio/virtio-net.h | 6 +-
include/net/net.h | 20 +++
net/tap-linux.h | 2 +
net/tap_int.h | 3 +
hw/core/qdev-properties.c | 66 ++++++++-
hw/net/virtio-net.c | 327 +++++++++++++++++++++++++++++------------
net/net.c | 14 ++
net/tap-bsd.c | 10 ++
net/tap-linux.c | 18 +++
net/tap-solaris.c | 10 ++
net/tap-stub.c | 10 ++
net/tap.c | 15 ++
net/vhost-vdpa.c | 41 +++++-
15 files changed, 473 insertions(+), 110 deletions(-)
---
base-commit: decf357a35b1201b34cc37c47b4b027f9601855e
change-id: 20240828-hash-628329a45d4d
Best regards,
--
Akihiko Odaki <akihiko.odaki@daynix.com>
next reply other threads:[~2024-09-15 1:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 1:23 Akihiko Odaki [this message]
2024-09-15 1:23 ` [PATCH RFC v3 01/11] qdev-properties: DEFINE_PROP_ON_OFF_AUTO_BIT() Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 02/11] net/vhost-vdpa: Report hashing capability Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 03/11] virtio-net: Move virtio_net_get_features() down Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 04/11] virtio-net: Retrieve peer hashing capability Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 05/11] net/vhost-vdpa: Remove dummy SetSteeringEBPF Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 06/11] virtio-net: Add hash type options Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 07/11] net: Allow configuring virtio hashing Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 08/11] virtio-net: Use qemu_set_vnet_hash() Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 09/11] virtio-net: Offload hashing without vhost Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 10/11] tap: Report virtio-net hashing support on Linux Akihiko Odaki
2024-09-15 1:23 ` [PATCH RFC v3 11/11] docs/devel/ebpf_rss.rst: Update for peer RSS Akihiko Odaki
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=20240915-hash-v3-0-79cb08d28647@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=andrew@daynix.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yuri.benditovich@daynix.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).