From: "Nambiar, Amritha" <amritha.nambiar@intel.com>
To: David Laight <David.Laight@ACULAB.COM>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "sridhar.samudrala@intel.com" <sridhar.samudrala@intel.com>
Subject: Re: [net-next PATCH v2 0/9] Introduce NAPI queues support
Date: Wed, 23 Aug 2023 16:49:17 -0700 [thread overview]
Message-ID: <35f733b5-577e-4529-b63b-30dc1d6568e5@intel.com> (raw)
In-Reply-To: <22603595289e4e86b6d61f0146b2e25d@AcuMS.aculab.com>
On 8/23/2023 3:24 AM, David Laight wrote:
> From: Amritha Nambiar
>> Sent: Tuesday, August 22, 2023 12:25 AM
>>
>> Introduce support for associating NAPI instances with
>> corresponding RX and TX queue set. Add the capability
>> to export NAPI information supported by the device.
>> Extend the netdev_genl generic netlink family for netdev
>> with NAPI data. The NAPI fields exposed are:
>> - NAPI id
>> - NAPI device ifindex
>> - queue/queue-set (both RX and TX) associated with each
>> NAPI instance
>> - Interrupt number associated with the NAPI instance
>> - PID for the NAPI thread
>>
>> This series only supports 'get' ability for retrieving
>> certain NAPI attributes. The 'set' ability for setting
>> queue[s] associated with a NAPI instance via netdev-genl
>> will be submitted as a separate patch series.
>>
>> Previous discussion at:
>> https://lore.kernel.org/netdev/c8476530638a5f4381d64db0e024ed49c2db3b02.camel@gmail.com/T/#m00999652a8
>> b4731fbdb7bf698d2e3666c65a60e7
>
> Not of this answers: what is it for?
The use-case is to limit the number of napi instances for the queues
within a queue-group. Other discussions at
https://lore.kernel.org/netdev/20230524111259.1323415-2-bigeasy@linutronix.de/
also explains the need.
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
prev parent reply other threads:[~2023-08-23 23:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 23:25 [net-next PATCH v2 0/9] Introduce NAPI queues support Amritha Nambiar
2023-08-21 23:25 ` [net-next PATCH v2 1/9] net: Introduce new fields for napi and queue associations Amritha Nambiar
2023-08-21 23:25 ` [net-next PATCH v2 2/9] ice: Add support in the driver for associating napi with queue[s] Amritha Nambiar
2023-08-21 23:25 ` [net-next PATCH v2 3/9] netdev-genl: spec: Extend netdev netlink spec in YAML for NAPI Amritha Nambiar
2023-08-23 0:39 ` Jakub Kicinski
2023-08-24 0:46 ` Nambiar, Amritha
2023-08-24 1:34 ` Jakub Kicinski
2023-08-24 22:26 ` Nambiar, Amritha
2023-08-24 23:55 ` Jakub Kicinski
2023-08-21 23:25 ` [net-next PATCH v2 4/9] net: Move kernel helpers for queue index outside sysfs Amritha Nambiar
2023-08-23 0:40 ` Jakub Kicinski
2023-08-23 23:57 ` Nambiar, Amritha
2023-08-21 23:25 ` [net-next PATCH v2 5/9] netdev-genl: Add netlink framework functions for napi Amritha Nambiar
2023-08-23 0:51 ` Jakub Kicinski
2023-08-23 23:53 ` Nambiar, Amritha
2023-08-21 23:25 ` [net-next PATCH v2 6/9] netdev-genl: spec: Add irq in netdev netlink YAML spec Amritha Nambiar
2023-08-21 23:25 ` [net-next PATCH v2 7/9] net: Add NAPI IRQ support Amritha Nambiar
2023-08-23 0:52 ` Jakub Kicinski
2023-08-23 23:49 ` Nambiar, Amritha
2023-08-21 23:25 ` [net-next PATCH v2 8/9] netdev-genl: spec: Add PID in netdev netlink YAML spec Amritha Nambiar
2023-08-21 23:25 ` [net-next PATCH v2 9/9] netdev-genl: Add PID for the NAPI thread Amritha Nambiar
2023-08-23 10:24 ` [net-next PATCH v2 0/9] Introduce NAPI queues support David Laight
2023-08-23 23:49 ` Nambiar, Amritha [this message]
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=35f733b5-577e-4529-b63b-30dc1d6568e5@intel.com \
--to=amritha.nambiar@intel.com \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--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).