From: Paolo Abeni <pabeni@redhat.com>
To: Amritha Nambiar <amritha.nambiar@intel.com>,
netdev@vger.kernel.org, kuba@kernel.org
Cc: sridhar.samudrala@intel.com
Subject: Re: [net-next PATCH v3 01/10] netdev-genl: spec: Extend netdev netlink spec in YAML for queue
Date: Thu, 28 Sep 2023 12:33:08 +0200 [thread overview]
Message-ID: <7b83b400cff5ecb7e150e4c0a4bca861ff08b392.camel@redhat.com> (raw)
In-Reply-To: <169516244040.7377.16515332696427625794.stgit@anambiarhost.jf.intel.com>
On Tue, 2023-09-19 at 15:27 -0700, Amritha Nambiar wrote:
> Add support in netlink spec(netdev.yaml) for queue information.
> Add code generated from the spec.
>
> Note: The "q-type" attribute currently takes values 0 and 1 for rx
> and tx queue type respectively. I haven't figured out the ynl
> library changes to support string user input ("rx" and "tx") to
> enum value conversion in the generated file.
>
> Signed-off-by: Amritha Nambiar <amritha.nambiar@intel.com>
> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> ---
> Documentation/netlink/specs/netdev.yaml | 52 ++++++++++
> include/uapi/linux/netdev.h | 17 +++
> net/core/netdev-genl-gen.c | 26 +++++
> net/core/netdev-genl-gen.h | 3 +
> net/core/netdev-genl.c | 10 ++
> tools/include/uapi/linux/netdev.h | 17 +++
> tools/net/ynl/generated/netdev-user.c | 159 +++++++++++++++++++++++++++++++
> tools/net/ynl/generated/netdev-user.h | 101 ++++++++++++++++++++
> 8 files changed, 385 insertions(+)
>
> diff --git a/Documentation/netlink/specs/netdev.yaml b/Documentation/netlink/specs/netdev.yaml
> index c46fcc78fc04..7b5d4cdff48b 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:
> -
> @@ -89,6 +93,32 @@ attribute-sets:
> enum: xdp-rx-metadata
> enum-as-flags: true
>
> + -
> + name: queue
> + attributes:
> + -
> + name: q-id
Why not 'queue-id' or 'id'?
> + doc: queue index
> + type: u32
> + -
> + name: ifindex
> + doc: netdev ifindex
> + type: u32
> + checks:
> + min: 1
> + -
> + name: q-type
Same here?
Cheers,
Paolo
next prev parent reply other threads:[~2023-09-28 10:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 22:27 [net-next PATCH v3 00/10] Introduce queue and NAPI support in netdev-genl (Was: Introduce NAPI queues support) Amritha Nambiar
2023-09-19 22:27 ` [net-next PATCH v3 01/10] netdev-genl: spec: Extend netdev netlink spec in YAML for queue Amritha Nambiar
2023-09-28 10:33 ` Paolo Abeni [this message]
2023-09-28 23:06 ` Nambiar, Amritha
2023-09-19 22:27 ` [net-next PATCH v3 02/10] net: Add queue and napi association Amritha Nambiar
2023-09-28 10:47 ` Paolo Abeni
2023-09-28 23:12 ` Nambiar, Amritha
2023-09-19 22:27 ` [net-next PATCH v3 03/10] ice: Add support in the driver for associating queue with napi Amritha Nambiar
2023-09-19 22:27 ` [net-next PATCH v3 04/10] netdev-genl: Add netlink framework functions for queue Amritha Nambiar
2023-10-10 9:08 ` Paolo Abeni
2023-10-10 19:57 ` Nambiar, Amritha
2023-09-19 22:27 ` [net-next PATCH v3 05/10] netdev-genl: spec: Extend netdev netlink spec in YAML for NAPI Amritha Nambiar
2023-09-19 22:27 ` [net-next PATCH v3 06/10] netdev-genl: Add netlink framework functions for napi Amritha Nambiar
2023-09-28 11:19 ` Paolo Abeni
2023-09-28 23:34 ` Nambiar, Amritha
2023-09-19 22:27 ` [net-next PATCH v3 07/10] netdev-genl: spec: Add irq in netdev netlink YAML spec Amritha Nambiar
2023-09-19 22:27 ` [net-next PATCH v3 08/10] net: Add NAPI IRQ support Amritha Nambiar
2023-09-19 22:28 ` [net-next PATCH v3 09/10] netdev-genl: spec: Add PID in netdev netlink YAML spec Amritha Nambiar
2023-09-19 22:28 ` [net-next PATCH v3 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=7b83b400cff5ecb7e150e4c0a4bca861ff08b392.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=amritha.nambiar@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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).