From: Jakub Kicinski <kuba@kernel.org>
To: "Mogilappagari, Sudheer" <sudheer.mogilappagari@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"mkubecek@suse.cz" <mkubecek@suse.cz>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"corbet@lwn.net" <corbet@lwn.net>,
"Samudrala, Sridhar" <sridhar.samudrala@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH net-next v5] ethtool: add netlink based get rss support
Date: Mon, 28 Nov 2022 15:24:23 -0800 [thread overview]
Message-ID: <20221128152423.0cc29e10@kernel.org> (raw)
In-Reply-To: <IA1PR11MB626656578C50634B3C90E0C4E40E9@IA1PR11MB6266.namprd11.prod.outlook.com>
On Fri, 25 Nov 2022 22:19:22 +0000 Mogilappagari, Sudheer wrote:
> > Let's not put the number of rings in RSS.
> >
> > I keep having to explain to people how to calculate the correct number
> > of active RX rings. If the field is in the channels API hopefully
> > they'll just use it.
> >
> > The max ring being in RXFH seems like a purely historic / legacy thing.
>
> Yes. channels API has this information. If ring count is not recommended in
> RSS_GET, any possibility of excluding rings info from ethtool output too?
> Included rings attribute in RSS_GET because user space code gets simplified
> while maintaining backward compatibility of output.
>
> I assume same output needs to be maintained. So, will have user space code
> doing CHANNELS_GET and RSS_GET during ethtool -x.
>
> $ ethtool -x eth0
> RX flow hash indirection table for eth0 with 56 RX ring(s): <<<
> 0: 0 1 2 3 4 5 6 7
I didn't recall the ring count being listed there. I would not be
against dropping it. Otherwise lets read the value via the channels
command. Simple matter of coding, as they say.
prev parent reply other threads:[~2022-11-28 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 18:48 [PATCH net-next v5] ethtool: add netlink based get rss support Sudheer Mogilappagari
2022-11-23 19:54 ` Michal Kubecek
2022-11-24 3:30 ` Jakub Kicinski
2022-11-25 22:19 ` Mogilappagari, Sudheer
2022-11-28 23:24 ` Jakub Kicinski [this message]
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=20221128152423.0cc29e10@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=sudheer.mogilappagari@intel.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).