public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Srujana Challa <schalla@marvell.com>,
	Willem de Bruijn <willemb@google.com>
Cc: <netdev@vger.kernel.org>, <virtualization@lists.linux.dev>,
	<pabeni@redhat.com>, <mst@redhat.com>, <jasowang@redhat.com>,
	<xuanzhuo@linux.alibaba.com>, <eperezma@redhat.com>,
	<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <ndabilpuram@marvell.com>,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Subject: Re: [PATCH net-next] virtio_net: Increase RSS max key size to match NETDEV_RSS_KEY_LEN
Date: Thu, 22 Jan 2026 07:52:06 -0800	[thread overview]
Message-ID: <20260122075206.504ec591@kernel.org> (raw)
In-Reply-To: <20260122091527.339180-1-schalla@marvell.com>

On Thu, 22 Jan 2026 14:45:27 +0530 Srujana Challa wrote:
> Increase VIRTIO_NET_RSS_MAX_KEY_SIZE from 40 to 52 bytes to align with
> the kernel's standard RSS key length defined by NETDEV_RSS_KEY_LEN.

I've been meaning to bump NETDEV_RSS_KEY_LEN to 128 or some such.
Most modern drivers can't use netdev_rss_key_fill() either because
core generates a tiny key. And the devices support hashing over two
layers of IPv6 for tunnels.

Willem, WDYT? Is there a reason to keep the core key small?
Or deprecate netdev_rss_key_fill()?

> The virtio specification requires devices to support at least 40 bytes
> for the RSS key size. However, devices may support larger key sizes
> up to 52 bytes (as reported by the device's rss_max_key_size config
> field). This change allows such devices to work properly.
> Previously, devices reporting rss_max_key_size > 40 would fail with
> an error during initialization.
> 
> The driver already handles variable key sizes dynamically through
> vi->rss_key_size, so increasing the maximum limit is safe and
> maintains backward compatibility with devices that support smaller
> key sizes.

> -#define VIRTIO_NET_RSS_MAX_KEY_SIZE     40
> +#define VIRTIO_NET_RSS_MAX_KEY_SIZE     52

  parent reply	other threads:[~2026-01-22 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22  9:15 [PATCH net-next] virtio_net: Increase RSS max key size to match NETDEV_RSS_KEY_LEN Srujana Challa
2026-01-22 10:15 ` Michael S. Tsirkin
2026-01-23 11:37   ` [EXTERNAL] " Srujana Challa
2026-01-22 15:52 ` Jakub Kicinski [this message]
2026-01-22 16:13   ` Eric Dumazet
2026-01-22 16:17     ` Eric Dumazet
2026-01-22 16:52     ` Jakub Kicinski
2026-01-22 19:32     ` Willem de Bruijn
2026-01-22 19:42       ` Willem de Bruijn
2026-01-23 11:46   ` [EXTERNAL] " Srujana Challa

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=20260122075206.504ec591@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=ndabilpuram@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=schalla@marvell.com \
    --cc=virtualization@lists.linux.dev \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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