From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Shuah Khan <shuah@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kselftest@vger.kernel.org,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Andrew Melnychenko <andrew@daynix.com>,
Stephen Hemminger <stephen@networkplumber.org>,
gur.stavi@huawei.com, Lei Yang <leiyang@redhat.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next v9 3/6] tun: Introduce virtio-net hash feature
Date: Mon, 10 Mar 2025 17:16:41 +0900 [thread overview]
Message-ID: <5cfedd24-de7c-484b-afa7-ddb4828fb9e8@daynix.com> (raw)
In-Reply-To: <CACGkMEtCEwSB7XvCg7_8ebkcM8o2s8JB2Err2f153L-_i2KtxA@mail.gmail.com>
On 2025/03/10 13:01, Jason Wang wrote:
> On Mon, Mar 10, 2025 at 11:55 AM Jason Wang <jasowang@redhat.com> wrote:
>>
>> On Fri, Mar 7, 2025 at 7:01 PM Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
>>>
>>> Hash reporting
>>> ==============
>>>
>>> Allow the guest to reuse the hash value to make receive steering
>>> consistent between the host and guest, and to save hash computation.
>>>
>>> RSS
>>> ===
>>>
>>> RSS is a receive steering algorithm that can be negotiated to use with
>>> virtio_net. Conventionally the hash calculation was done by the VMM.
>>> However, computing the hash after the queue was chosen defeats the
>>> purpose of RSS.
>>>
>>> Another approach is to use eBPF steering program. This approach has
>>> another downside: it cannot report the calculated hash due to the
>>> restrictive nature of eBPF steering program.
>>>
>>> Introduce the code to perform RSS to the kernel in order to overcome
>>> thse challenges. An alternative solution is to extend the eBPF steering
>>> program so that it will be able to report to the userspace, but I didn't
>>> opt for it because extending the current mechanism of eBPF steering
>>> program as is because it relies on legacy context rewriting, and
>>> introducing kfunc-based eBPF will result in non-UAPI dependency while
>>> the other relevant virtualization APIs such as KVM and vhost_net are
>>> UAPIs.
>>>
>>> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>>> Tested-by: Lei Yang <leiyang@redhat.com>
>>> ---
>>> Documentation/networking/tuntap.rst | 7 ++
>>> drivers/net/Kconfig | 1 +
>>> drivers/net/tap.c | 68 ++++++++++++++-
>>> drivers/net/tun.c | 98 +++++++++++++++++-----
>>> drivers/net/tun_vnet.h | 159 ++++++++++++++++++++++++++++++++++--
>>> include/linux/if_tap.h | 2 +
>>> include/linux/skbuff.h | 3 +
>>> include/uapi/linux/if_tun.h | 75 +++++++++++++++++
>>> net/core/skbuff.c | 4 +
>>> 9 files changed, 386 insertions(+), 31 deletions(-)
>
> [...]
>
>>> + *
>>> + * The %TUN_VNET_HASH_REPORT flag set with this ioctl will be effective only
>>> + * after calling the %TUNSETVNETHDRSZ ioctl with a number greater than or equal
>>> + * to the size of &struct virtio_net_hdr_v1_hash.
>>
>> So you had a dependency check already for vnet hdr len. I'd still
>> suggest to split this into rss and hash as they are separated
>> features. Then we can use separate data structure for them instead of
>> a container struct.
>>
>
> Besides this, I think we still need to add new bits to TUNGETIFF to
> let userspace know about the new ability.
The userspace can peform TUNGETVNETHASHCAP and see if it results in EINVAL.
Regards,
Akihiko Odaki
>
> Thanks
>
next prev parent reply other threads:[~2025-03-10 8:16 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 11:01 [PATCH net-next v9 0/6] tun: Introduce virtio-net hashing feature Akihiko Odaki
2025-03-07 11:01 ` [PATCH net-next v9 1/6] virtio_net: Add functions for hashing Akihiko Odaki
2025-03-10 3:55 ` Jason Wang
2025-03-10 6:53 ` Akihiko Odaki
2025-03-11 0:47 ` Jason Wang
2025-03-11 5:49 ` Akihiko Odaki
2025-03-17 1:24 ` Jason Wang
2025-03-17 6:08 ` Akihiko Odaki
2025-03-07 11:01 ` [PATCH net-next v9 2/6] net: flow_dissector: Export flow_keys_dissector_symmetric Akihiko Odaki
2025-03-07 11:01 ` [PATCH net-next v9 3/6] tun: Introduce virtio-net hash feature Akihiko Odaki
2025-03-08 19:32 ` Willem de Bruijn
2025-03-10 7:11 ` Akihiko Odaki
2025-03-10 3:55 ` Jason Wang
2025-03-10 4:01 ` Jason Wang
2025-03-10 8:16 ` Akihiko Odaki [this message]
2025-03-10 7:45 ` Akihiko Odaki
2025-03-11 0:38 ` Jason Wang
2025-03-11 6:11 ` Akihiko Odaki
2025-03-12 2:35 ` Jason Wang
2025-03-12 5:03 ` Akihiko Odaki
2025-03-17 1:12 ` Jason Wang
2025-03-17 7:06 ` Akihiko Odaki
2025-03-18 0:15 ` Jason Wang
2025-03-18 10:10 ` Akihiko Odaki
2025-03-19 0:58 ` Jason Wang
2025-03-19 5:28 ` Akihiko Odaki
2025-03-20 1:31 ` Jason Wang
2025-03-20 5:33 ` Akihiko Odaki
2025-03-21 1:13 ` Jason Wang
2025-03-21 5:56 ` Akihiko Odaki
2025-03-24 4:40 ` Jason Wang
2025-03-29 9:15 ` Akihiko Odaki
2025-03-11 6:17 ` Akihiko Odaki
2025-03-12 2:59 ` Jason Wang
2025-03-12 5:55 ` Akihiko Odaki
2025-03-17 1:15 ` Jason Wang
2025-03-10 7:58 ` Akihiko Odaki
2025-03-11 0:40 ` Jason Wang
2025-03-10 8:13 ` Akihiko Odaki
2025-03-07 11:01 ` [PATCH net-next v9 4/6] selftest: tun: Test vnet ioctls without device Akihiko Odaki
2025-03-07 11:01 ` [PATCH net-next v9 5/6] selftest: tun: Add tests for virtio-net hashing Akihiko Odaki
2025-03-08 19:39 ` Willem de Bruijn
2025-03-10 4:03 ` Jason Wang
2025-03-11 6:19 ` Akihiko Odaki
2025-03-07 11:01 ` [PATCH net-next v9 6/6] vhost/net: Support VIRTIO_NET_F_HASH_REPORT Akihiko Odaki
2025-03-10 4:43 ` Jason Wang
2025-03-10 7:04 ` Akihiko Odaki
2025-03-11 0:42 ` Jason Wang
2025-03-11 6:24 ` Akihiko Odaki
2025-03-12 3:36 ` Jason Wang
2025-03-12 5:59 ` Akihiko Odaki
2025-03-17 1:15 ` Jason Wang
2025-03-19 4:43 ` Akihiko Odaki
2025-03-13 1:15 ` [PATCH net-next v9 0/6] tun: Introduce virtio-net hashing feature Lei Yang
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=5cfedd24-de7c-484b-afa7-ddb4828fb9e8@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=andrew@daynix.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gur.stavi@huawei.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leiyang@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stephen@networkplumber.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xuanzhuo@linux.alibaba.com \
--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).