From: Joe Damato <jdamato@fastly.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, dxu@dxuuu.xyz, ecree.xilinx@gmail.com,
przemyslaw.kitszel@intel.com, donald.hunter@gmail.com,
gal.pressman@linux.dev, tariqt@nvidia.com,
willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH net-next 06/12] ethtool: rss: don't report key if device doesn't support it
Date: Fri, 2 Aug 2024 12:58:34 +0100 [thread overview]
Message-ID: <ZqzJ6tLil3vwvfgh@LQ3V64L9R2> (raw)
In-Reply-To: <20240802001801.565176-7-kuba@kernel.org>
On Thu, Aug 01, 2024 at 05:17:55PM -0700, Jakub Kicinski wrote:
> marvell/otx2 and mvpp2 do not support setting different
> keys for different RSS contexts. Contexts have separate
> indirection tables but key is shared with all other contexts.
> This is likely fine, indirection table is the most important
> piece.
>
> Don't report the key-related parameters from such drivers.
> This prevents driver-errors, e.g. otx2 always writes
> the main key, even when user asks to change per-context key.
> The second reason is that without this change tracking
> the keys by the core gets complicated. Even if the driver
> correctly reject setting key with rss_context != 0,
> change of the main key would have to be reflected in
> the XArray for all additional contexts.
>
> Since the additional contexts don't have their own keys
> not including the attributes (in Netlink speak) seems
> intuitive. ethtool CLI seems to deal with it just fine.
FWIW: I took a look at the ethtool source and I agree, but didn't
test it.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> .../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 1 +
> drivers/net/ethernet/intel/ice/ice_ethtool.c | 1 +
> .../ethernet/mellanox/mlx5/core/en_ethtool.c | 1 +
> drivers/net/ethernet/sfc/ef100_ethtool.c | 1 +
> drivers/net/ethernet/sfc/ethtool.c | 1 +
> drivers/net/ethernet/sfc/siena/ethtool.c | 1 +
> include/linux/ethtool.h | 3 +++
> net/ethtool/ioctl.c | 25 ++++++++++++++++---
> net/ethtool/rss.c | 21 +++++++++++-----
> 9 files changed, 45 insertions(+), 10 deletions(-)
Reviewed-by: Joe Damato <jdamato@fastly.com>
next prev parent reply other threads:[~2024-08-02 11:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 0:17 [PATCH net-next 00/12] ethtool: rss: driver tweaks and netlink context dumps Jakub Kicinski
2024-08-02 0:17 ` [PATCH net-next 01/12] selftests: drv-net: rss_ctx: add identifier to traffic comments Jakub Kicinski
2024-08-02 11:23 ` Joe Damato
2024-08-02 0:17 ` [PATCH net-next 02/12] eth: mvpp2: implement new RSS context API Jakub Kicinski
2024-08-02 0:17 ` [PATCH net-next 03/12] eth: mlx5: allow disabling queues when RSS contexts exist Jakub Kicinski
2024-08-02 11:27 ` Joe Damato
2024-08-02 0:17 ` [PATCH net-next 04/12] ethtool: make ethtool_ops::cap_rss_ctx_supported optional Jakub Kicinski
2024-08-02 11:35 ` Joe Damato
2024-08-02 0:17 ` [PATCH net-next 05/12] eth: remove .cap_rss_ctx_supported from updated drivers Jakub Kicinski
2024-08-02 11:41 ` Joe Damato
2024-08-02 0:17 ` [PATCH net-next 06/12] ethtool: rss: don't report key if device doesn't support it Jakub Kicinski
2024-08-02 11:58 ` Joe Damato [this message]
2024-08-02 0:17 ` [PATCH net-next 07/12] ethtool: rss: move the device op invocation out of rss_prepare_data() Jakub Kicinski
2024-08-02 13:15 ` Joe Damato
2024-08-02 0:17 ` [PATCH net-next 08/12] ethtool: rss: report info about additional contexts from XArray Jakub Kicinski
2024-08-02 13:18 ` Joe Damato
2024-08-02 0:17 ` [PATCH net-next 09/12] ethtool: rss: support dumping RSS contexts Jakub Kicinski
2024-08-02 0:17 ` [PATCH net-next 10/12] ethtool: rss: support skipping contexts during dump Jakub Kicinski
2024-08-02 0:18 ` [PATCH net-next 11/12] netlink: specs: decode indirection table as u32 array Jakub Kicinski
2024-08-02 0:18 ` [PATCH net-next 12/12] selftests: drv-net: rss_ctx: test dumping RSS contexts Jakub Kicinski
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=ZqzJ6tLil3vwvfgh@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dxu@dxuuu.xyz \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=gal.pressman@linux.dev \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tariqt@nvidia.com \
--cc=willemdebruijn.kernel@gmail.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