netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: Joe Damato <jdamato@fastly.com>, Daniel Xu <dxu@dxuuu.xyz>,
	davem@davemloft.net, mkubecek@suse.cz, martin.lau@linux.dev,
	netdev@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH ethtool-next] rxclass: Make output for RSS context action explicit
Date: Mon, 11 Nov 2024 10:22:18 -0800	[thread overview]
Message-ID: <20241111102218.0e1b3ac9@kernel.org> (raw)
In-Reply-To: <7724370d-5e8a-bf98-421a-3a69294daa8c@gmail.com>

On Mon, 11 Nov 2024 10:47:47 +0000 Edward Cree wrote:
> On 09/11/2024 17:42, Jakub Kicinski wrote:
> > I'd suggest we merge Daniel's patch (almost) as is, and you can
> > (re)establish the behavior sfc wants but you owe us:
> >  - fixes for helpers used in "is the queue in use" checks like
> >    ethtool_get_max_rss_ctx_channel()
> >  - "opt in" flag for drivers which actually support this rather 
> >    than silently ignoring ring_cookie if rss ctx is set
> >  - selftest  
> 
> Sure, I'll get to work on those.
> But I don't think Daniel's patch should be merged; the old output
>  is confusing or misleading, but the new output is incorrect (when
>  run against a current kernel and sfc, or a future fixed kernel and
>  any driver that opts in to allow nonzero ring_cookie).
> If ring_cookie is nonzero then it *must* be printed, unless ethtool
>  has some way to *know* it's ignored.  Regressions are worse than
>  existing bugs, after all.

If you promise sending patches for the kernel side validation soon -
printing when non-zero makes sense :)

  reply	other threads:[~2024-11-11 18:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 19:32 [PATCH ethtool-next] rxclass: Make output for RSS context action explicit Daniel Xu
2024-11-08 19:35 ` Daniel Xu
2024-11-08 19:56 ` Edward Cree
2024-11-08 20:34   ` Joe Damato
2024-11-08 20:43     ` Joe Damato
2024-11-08 21:13     ` Edward Cree
2024-11-08 22:50       ` Daniel Xu
2024-11-09 17:42       ` Jakub Kicinski
2024-11-11 10:47         ` Edward Cree
2024-11-11 18:22           ` Jakub Kicinski [this message]
2024-11-12  9:24         ` Edward Cree
2024-11-12 15:24           ` Jakub Kicinski
2024-11-13  3:30             ` Edward Cree
2024-11-14  0:46               ` Jakub Kicinski
2024-11-14  0:46                 ` Jakub Kicinski
2024-11-14 23:04                 ` Edward Cree

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=20241111102218.0e1b3ac9@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dxu@dxuuu.xyz \
    --cc=ecree.xilinx@gmail.com \
    --cc=jdamato@fastly.com \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@linux.dev \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    /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).