[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c21aa836-a197-6c63-2843-ec6db4faa3be@intel.com>
Date: Mon, 31 Jul 2023 17:24:51 -0700
From: "Nambiar, Amritha" <amritha.nambiar@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <netdev@...r.kernel.org>, <davem@...emloft.net>,
<sridhar.samudrala@...el.com>
Subject: Re: [net-next PATCH v1 3/9] netdev-genl: spec: Extend netdev netlink
spec in YAML for NAPI
On 7/31/2023 5:13 PM, Jakub Kicinski wrote:
> On Mon, 31 Jul 2023 16:12:23 -0700 Nambiar, Amritha wrote:
>>> Every NAPI instance should be dumped as a separate object. We can
>>> implemented filtered dump to get NAPIs of a single netdev.
>>
>> Today, the 'do napi-get <ifindex>' will show all the NAPIs for a single
>> netdev:
>> Example: --do napi-get --json='{"ifindex": 6}'
>>
>> and the 'dump napi-get' will dump all the NAPIs for all the netdevs.
>> Example: netdev.yaml --dump napi-get
>>
>> Are you suggesting that we also dump each NAPI instance individually,
>> 'do napi-get <ifindex> <NAPI_ID>'
>>
>> Example:
>> netdev.yaml --do napi-get --json='{"ifindex": 6, "napi-id": 390}'
>>
>> [{'ifindex': 6},
>> {'napi-info': [{'irq': 296,
>> 'napi-id': 390,
>> 'pid': 3475,
>> 'rx-queues': [5],
>> 'tx-queues': [5]}]}]
>
> Dumps can be filtered, I'm saying:
>
> $ netdev.yaml --dump napi-get --json='{"ifindex": 6}'
> ^^^^
>
> [{'napi-id': 390, 'ifindex': 6, 'irq': 296, ...},
> {'napi-id': 391, 'ifindex': 6, 'irq': 297, ...}]
I see. Okay. Looks like this needs to be supported for "dump dev-get
ifindex" as well.
Powered by blists - more mailing lists