public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>,
	 Jonathan Corbet <corbet@lwn.net>,
	 Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	 Jason Wang <jasowang@redhat.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,  Akihiko Odaki <akihiko.odaki@daynix.com>
Subject: Re: [PATCH v6 1/6] virtio_net: Add functions for hashing
Date: Thu, 09 Jan 2025 09:13:33 -0500	[thread overview]
Message-ID: <677fd98d89df1_362bc12942f@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20250109-rss-v6-1-b1c90ad708f6@daynix.com>

Akihiko Odaki wrote:
> They are useful to implement VIRTIO_NET_F_RSS and
> VIRTIO_NET_F_HASH_REPORT.

Toeplitz potentially has users beyond virtio. I wonder if we should
from the start implement this as net/core/rss.c.

 
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
>  include/linux/virtio_net.h | 188 +++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 188 insertions(+)
> 
> diff --git a/include/linux/virtio_net.h b/include/linux/virtio_net.h
> index 02a9f4dc594d..3b25ca75710b 100644
> --- a/include/linux/virtio_net.h
> +++ b/include/linux/virtio_net.h
> @@ -9,6 +9,194 @@
>  #include <uapi/linux/tcp.h>
>  #include <uapi/linux/virtio_net.h>
>  
> +struct virtio_net_hash {
> +	u32 value;
> +	u16 report;
> +};
> +
> +struct virtio_net_toeplitz_state {
> +	u32 hash;
> +	const u32 *key;
> +};
> +
> +#define VIRTIO_NET_SUPPORTED_HASH_TYPES (VIRTIO_NET_RSS_HASH_TYPE_IPv4 | \
> +					 VIRTIO_NET_RSS_HASH_TYPE_TCPv4 | \
> +					 VIRTIO_NET_RSS_HASH_TYPE_UDPv4 | \
> +					 VIRTIO_NET_RSS_HASH_TYPE_IPv6 | \
> +					 VIRTIO_NET_RSS_HASH_TYPE_TCPv6 | \
> +					 VIRTIO_NET_RSS_HASH_TYPE_UDPv6)
> +
> +#define VIRTIO_NET_RSS_MAX_KEY_SIZE 40
> +
> +static inline void virtio_net_toeplitz_convert_key(u32 *input, size_t len)
> +{
> +	while (len >= sizeof(*input)) {
> +		*input = be32_to_cpu((__force __be32)*input);
> +		input++;
> +		len -= sizeof(*input);
> +	}
> +}
> +
> +static inline void virtio_net_toeplitz_calc(struct virtio_net_toeplitz_state *state,
> +					    const __be32 *input, size_t len)
> +{
> +	while (len >= sizeof(*input)) {
> +		for (u32 map = be32_to_cpu(*input); map; map &= (map - 1)) {
> +			u32 i = ffs(map);
> +
> +			state->hash ^= state->key[0] << (32 - i) |
> +				       (u32)((u64)state->key[1] >> i);
> +		}
> +
> +		state->key++;
> +		input++;
> +		len -= sizeof(*input);
> +	}
> +}

Have you verified that this algorithm matches a known toeplitz
implementation. And computes the expected values for the test
inputs in

https://learn.microsoft.com/en-us/windows-hardware/drivers/network/verifying-the-rss-hash-calculation

We have a toeplitz implementation in
tools/testing/selftests/net/toeplitz.c that can also be used as
reference.

> +
> +static inline u8 virtio_net_hash_key_length(u32 types)
> +{
> +	size_t len = 0;
> +
> +	if (types & VIRTIO_NET_HASH_REPORT_IPv4)
> +		len = max(len,
> +			  sizeof(struct flow_dissector_key_ipv4_addrs));
> +
> +	if (types &
> +	    (VIRTIO_NET_HASH_REPORT_TCPv4 | VIRTIO_NET_HASH_REPORT_UDPv4))
> +		len = max(len,
> +			  sizeof(struct flow_dissector_key_ipv4_addrs) +
> +			  sizeof(struct flow_dissector_key_ports));
> +
> +	if (types & VIRTIO_NET_HASH_REPORT_IPv6)
> +		len = max(len,
> +			  sizeof(struct flow_dissector_key_ipv6_addrs));
> +
> +	if (types &
> +	    (VIRTIO_NET_HASH_REPORT_TCPv6 | VIRTIO_NET_HASH_REPORT_UDPv6))
> +		len = max(len,
> +			  sizeof(struct flow_dissector_key_ipv6_addrs) +
> +			  sizeof(struct flow_dissector_key_ports));
> +
> +	return len + 4;

Avoid magic constants. Please use sizeof or something else to signal
what this 4 derives from.

  reply	other threads:[~2025-01-09 14:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  7:13 [PATCH v6 0/6] tun: Introduce virtio-net hashing feature Akihiko Odaki
2025-01-09  7:13 ` [PATCH v6 1/6] virtio_net: Add functions for hashing Akihiko Odaki
2025-01-09 14:13   ` Willem de Bruijn [this message]
2025-01-10  9:28     ` Akihiko Odaki
2025-01-09  7:13 ` [PATCH v6 2/6] net: flow_dissector: Export flow_keys_dissector_symmetric Akihiko Odaki
2025-01-09  7:13 ` [PATCH v6 3/6] tun: Introduce virtio-net hash feature Akihiko Odaki
2025-01-09 14:28   ` Willem de Bruijn
2025-01-10  9:32     ` Akihiko Odaki
2025-01-09  7:13 ` [PATCH v6 4/6] selftest: tun: Test vnet ioctls without device Akihiko Odaki
2025-01-09  7:13 ` [PATCH v6 5/6] selftest: tun: Add tests for virtio-net hashing Akihiko Odaki
2025-01-09 14:36   ` Willem de Bruijn
2025-01-10  9:47     ` Akihiko Odaki
2025-01-09  7:13 ` [PATCH v6 6/6] vhost/net: Support VIRTIO_NET_F_HASH_REPORT Akihiko Odaki
2025-01-09 14:07 ` [PATCH v6 0/6] tun: Introduce virtio-net hashing feature Willem de Bruijn
2025-01-10  7:36   ` 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=677fd98d89df1_362bc12942f@willemb.c.googlers.com.notmuch \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=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=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --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=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