From: Stanislav Fomichev <stfomichev@gmail.com>
To: Samiullah Khawaja <skhawaja@google.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S . Miller " <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] Add support to set napi threaded for individual napi
Date: Thu, 2 Jan 2025 13:15:22 -0800 [thread overview]
Message-ID: <Z3cB6mcpi5eJCpca@mini-arch> (raw)
In-Reply-To: <20250102191227.2084046-2-skhawaja@google.com>
On 01/02, Samiullah Khawaja wrote:
> A net device has a threaded sysctl that can be used to enable threaded
> napi polling on all of the NAPI contexts under that device. Allow
> enabling threaded napi polling at individual napi level using netlink.
>
> Add a new netlink operation `napi-set-threaded` that takes napi `id` and
> `threaded` attributes. This will enable the threaded polling on napi
> context.
>
> Tested using following command in qemu/virtio-net:
> ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --do napi-set-threaded --json '{"id": 513, "threaded": 1}'
>
> Signed-off-by: Samiullah Khawaja <skhawaja@google.com>
> Reviewed-by: Willem de Bruijn <willemb@google.com>
> ---
> Documentation/netlink/specs/netdev.yaml | 19 +++++++++++++
> include/linux/netdevice.h | 9 ++++++
> include/uapi/linux/netdev.h | 2 ++
> net/core/dev.c | 26 +++++++++++++++++
> net/core/netdev-genl-gen.c | 13 +++++++++
> net/core/netdev-genl-gen.h | 2 ++
> net/core/netdev-genl.c | 37 +++++++++++++++++++++++++
> tools/include/uapi/linux/netdev.h | 2 ++
> 8 files changed, 110 insertions(+)
>
> diff --git a/Documentation/netlink/specs/netdev.yaml b/Documentation/netlink/specs/netdev.yaml
> index cbb544bd6c84..aac343af7246 100644
> --- a/Documentation/netlink/specs/netdev.yaml
> +++ b/Documentation/netlink/specs/netdev.yaml
> @@ -268,6 +268,14 @@ attribute-sets:
> doc: The timeout, in nanoseconds, of how long to suspend irq
> processing, if event polling finds events
> type: uint
> + -
> + name: threaded
> + doc: Whether the napi is configured to operate in threaded polling
> + mode. If this is set to `1` then the NAPI context operates
> + in threaded polling mode.
> + type: u32
> + checks:
> + max: 1
> -
> name: queue
> attributes:
> @@ -659,6 +667,7 @@ operations:
> - defer-hard-irqs
> - gro-flush-timeout
> - irq-suspend-timeout
> + - threaded
> dump:
> request:
> attributes:
> @@ -711,6 +720,16 @@ operations:
> - defer-hard-irqs
> - gro-flush-timeout
> - irq-suspend-timeout
> + -
> + name: napi-set-threaded
> + doc: Set threaded napi mode on this napi.
> + attribute-set: napi
> + flags: [ admin-perm ]
> + do:
> + request:
> + attributes:
> + - id
> + - threaded
Any reason we need a separate op to enable/disable? Why not piggyback
on napi_set?
Maybe also move 'threaded' flag to persistent napi config?
next prev parent reply other threads:[~2025-01-02 21:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 19:12 [PATCH net-next 0/3] Add support to do threaded napi busy poll Samiullah Khawaja
2025-01-02 19:12 ` [PATCH net-next 1/3] Add support to set napi threaded for individual napi Samiullah Khawaja
2025-01-02 21:15 ` Stanislav Fomichev [this message]
2025-01-02 19:12 ` [PATCH net-next 2/3] net: Create separate gro_flush helper function Samiullah Khawaja
2025-01-02 19:12 ` [PATCH net-next 3/3] Extend napi threaded polling to allow kthread based busy polling Samiullah Khawaja
2025-01-02 21:16 ` Samudrala, Sridhar
2025-01-02 21:28 ` Stanislav Fomichev
2025-01-03 1:05 ` kernel test robot
2025-01-03 8:11 ` kernel test robot
2025-01-03 8:12 ` kernel test robot
2025-01-02 21:30 ` [PATCH net-next 0/3] Add support to do threaded napi busy poll Stanislav Fomichev
2025-01-02 21:56 ` David Laight
2025-01-03 0:47 ` Jakub Kicinski
2025-01-08 19:25 ` Joe Damato
2025-01-08 21:18 ` Samiullah Khawaja
2025-01-08 21:53 ` Martin Karsten
2025-01-15 22:35 ` Samiullah Khawaja
2025-01-16 0:28 ` Martin Karsten
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=Z3cB6mcpi5eJCpca@mini-arch \
--to=stfomichev@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhawaja@google.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).