From: Jakub Kicinski <kuba@kernel.org>
To: Amritha Nambiar <amritha.nambiar@intel.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, sridhar.samudrala@intel.com
Subject: Re: [net-next PATCH v7 01/10] netdev-genl: spec: Extend netdev netlink spec in YAML for queue
Date: Tue, 14 Nov 2023 23:48:01 -0500 [thread overview]
Message-ID: <20231114234801.0faee5db@kernel.org> (raw)
In-Reply-To: <169992177699.3867.16531901770683676993.stgit@anambiarhost.jf.intel.com>
On Mon, 13 Nov 2023 16:29:37 -0800 Amritha Nambiar wrote:
> Add support in netlink spec(netdev.yaml) for queue information.
> Add code generated from the spec.
>
> Note: The "queue-type" attribute takes values 0 and 1 for rx
> and tx queue type respectively.
> index 14511b13f305..e7bf6007d77f 100644
> --- a/Documentation/netlink/specs/netdev.yaml
> +++ b/Documentation/netlink/specs/netdev.yaml
> @@ -55,6 +55,10 @@ definitions:
> name: hash
> doc:
> Device is capable of exposing receive packet hash via bpf_xdp_metadata_rx_hash().
> + -
> + name: queue-type
> + type: enum
> + entries: [ rx, tx ]
>
> attribute-sets:
> -
> @@ -87,6 +91,31 @@ attribute-sets:
> type: u64
> enum: xdp-rx-metadata
>
> + -
> + name: queue
> + attributes:
> + -
> + name: queue-id
Hm. I guess it looks okay in the Python / JSON but the C defines
will say NETDEV_QUEUE_QUEUE_ID or some such. Should we drop the word
queue from all attrs in the queue set?
Sorry, not sure how I missed this earlier. Some extra nits below while
I'm requesting changes...
> + doc: Queue index for most queue types are indexed like a C array, with
s/ for/;/ ?
> + indexes starting at 0 and ending at queue count - 1. Queue indexes
> + are scoped to an interface and queue type.
> + type: u32
> + -
> + name: ifindex
> + doc: ifindex of the netdevice to which the queue belongs.
> + type: u32
> + checks:
> + min: 1
> + -
> + name: queue-type
> + doc: queue type as rx, tx
Add: ". Each queue type defines a separate ID space."
> + type: u32
> + enum: queue-type
> + -
> + name: napi-id
> + doc: ID of the NAPI instance which services this queue.
> + type: u32
> +
> operations:
> list:
> -
> @@ -120,6 +149,29 @@ operations:
> doc: Notification about device configuration being changed.
> notify: dev-get
> mcgrp: mgmt
> + -
> + name: queue-get
> + doc: Get queue information from the kernel.
> + Only configured queues will be reported (as opposed to all available
> + queues).
maybe add "hardware", so "all available hardware queues)" ?
That may help the reader connect the dots
next prev parent reply other threads:[~2023-11-15 4:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 0:29 [net-next PATCH v7 00/10] Introduce queue and NAPI support in netdev-genl (Was: Introduce NAPI queues support) Amritha Nambiar
2023-11-14 0:29 ` [net-next PATCH v7 01/10] netdev-genl: spec: Extend netdev netlink spec in YAML for queue Amritha Nambiar
2023-11-15 4:48 ` Jakub Kicinski [this message]
2023-11-15 21:05 ` Nambiar, Amritha
2023-11-16 5:53 ` Jakub Kicinski
2023-11-14 0:29 ` [net-next PATCH v7 02/10] net: Add queue and napi association Amritha Nambiar
2023-11-14 0:29 ` [net-next PATCH v7 03/10] ice: Add support in the driver for associating queue with napi Amritha Nambiar
2023-11-14 0:29 ` [net-next PATCH v7 04/10] netdev-genl: Add netlink framework functions for queue Amritha Nambiar
2023-11-14 0:29 ` [net-next PATCH v7 05/10] netdev-genl: spec: Extend netdev netlink spec in YAML for NAPI Amritha Nambiar
2023-11-15 4:49 ` Jakub Kicinski
2023-11-14 0:30 ` [net-next PATCH v7 06/10] netdev-genl: Add netlink framework functions for napi Amritha Nambiar
2023-11-14 0:30 ` [net-next PATCH v7 07/10] netdev-genl: spec: Add irq in netdev netlink YAML spec Amritha Nambiar
2023-11-14 0:30 ` [net-next PATCH v7 08/10] net: Add NAPI IRQ support Amritha Nambiar
2023-11-14 0:30 ` [net-next PATCH v7 09/10] netdev-genl: spec: Add PID in netdev netlink YAML spec Amritha Nambiar
2023-11-14 0:30 ` [net-next PATCH v7 10/10] netdev-genl: Add PID for the NAPI thread Amritha Nambiar
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=20231114234801.0faee5db@kernel.org \
--to=kuba@kernel.org \
--cc=amritha.nambiar@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@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).