From: Jacob Keller <jacob.e.keller@intel.com>
To: "Mogilappagari, Sudheer" <sudheer.mogilappagari@intel.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Michal Kubecek <mkubecek@suse.cz>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH ethtool] netlink: rss: retrieve ring count using ETHTOOL_GRXRINGS ioctl
Date: Thu, 19 Sep 2024 10:58:48 -0700 [thread overview]
Message-ID: <45327ee6-e57c-4fec-bf43-86bd1338f5fb@intel.com> (raw)
In-Reply-To: <IA1PR11MB62661EF398124FC523CC3C03E4652@IA1PR11MB6266.namprd11.prod.outlook.com>
On 9/13/2024 4:07 PM, Mogilappagari, Sudheer wrote:
>
>
>> -----Original Message-----
>> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>> Sent: Friday, September 13, 2024 3:49 PM
>> To: Mogilappagari, Sudheer <sudheer.mogilappagari@intel.com>
>> Cc: netdev@vger.kernel.org; Michal Kubecek <mkubecek@suse.cz>; Jakub
>> Kicinski <kuba@kernel.org>
>> Subject: Re: [PATCH ethtool] netlink: rss: retrieve ring count using
>> ETHTOOL_GRXRINGS ioctl
>>
>> Hi Sudheer,
>>
>> On Fri, Sep 13, 2024 at 10:43:19PM +0000, Mogilappagari, Sudheer wrote:
>>> Hi Vladimir, my understanding is ioctls are not used in ethtool
>>> netlink path. Can we use ETHTOOL_MSG_RINGS_GET
>> (tb[ETHTOOL_A_RINGS_RX]
>>> member) instead ?
>>
>> You mean this?
>>
>> ``ETHTOOL_A_RINGS_RX`` u32 size of RX ring
>
> Yes. I had meant ETHTOOL_A_RINGS_RX but I see it is ring size and not ring
> count. There seems to be no netlink message that fetches ringcount info.
>
We could extend the netlink interface to add this over netlink instead
of ioctl, but that hasn't been done yet.
next prev parent reply other threads:[~2024-09-19 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 9:38 [PATCH ethtool] netlink: rss: retrieve ring count using ETHTOOL_GRXRINGS ioctl Vladimir Oltean
2024-09-13 20:34 ` Jakub Kicinski
2024-09-13 22:43 ` Mogilappagari, Sudheer
2024-09-13 22:45 ` Mogilappagari, Sudheer
2024-09-13 22:48 ` Vladimir Oltean
2024-09-13 23:07 ` Mogilappagari, Sudheer
2024-09-19 17:58 ` Jacob Keller [this message]
2024-10-03 9:18 ` Vladimir Oltean
2024-10-03 11:09 ` Michal Kubecek
2024-10-03 13:49 ` Vladimir Oltean
2024-10-03 23:20 ` Michal Kubecek
2024-10-04 19:19 ` Keller, Jacob E
2024-10-05 7:46 ` Michal Kubecek
2024-10-07 22:12 ` Jacob Keller
2024-09-16 19:38 ` Michal Kubecek
2024-09-17 15:10 ` 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=45327ee6-e57c-4fec-bf43-86bd1338f5fb@intel.com \
--to=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=sudheer.mogilappagari@intel.com \
--cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.