netdev - Re: [net-next PATCH v2 3/9] netdev-genl: spec: Extend netdev netlink spec in YAML for NAPI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 23 Aug 2023 18:34:36 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Nambiar, Amritha" <amritha.nambiar@...el.com>
Cc: <netdev@...r.kernel.org>, <davem@...emloft.net>,
 <sridhar.samudrala@...el.com>
Subject: Re: [net-next PATCH v2 3/9] netdev-genl: spec: Extend netdev
 netlink spec in YAML for NAPI

On Wed, 23 Aug 2023 17:46:20 -0700 Nambiar, Amritha wrote:
> Can we have both: "queue-get" (queue object with with NAPI-ID attr) and 
> "napi-get" (NAPI object with "set of queue IDs" as an attribute), 
> something like below (rx-queue is the queue object. rx-queues is the 
> list attr within the NAPI object):

I think just queue-get is better, the IDs of queues are not unique.
It's more of an index within a group than and identifier. 
Displaying information about e.g. XDP TX queues within would get messy.