[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250205231003.49e5cc3f@pumpkin>
Date: Wed, 5 Feb 2025 23:10:03 +0000
From: David Laight <david.laight.linux@...il.com>
To: Samiullah Khawaja <skhawaja@...gle.com>
Cc: Jakub Kicinski <kuba@...nel.org>, "David S . Miller "
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, almasrymina@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 1/4] Add support to set napi threaded for
individual napi
On Wed, 5 Feb 2025 00:10:49 +0000
Samiullah Khawaja <skhawaja@...gle.com> 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.
>
> Extend the netlink operation `napi-set` and allow setting the threaded
> attribute of a NAPI. This will enable the threaded polling on a napi
> context.
>
> Tested using following command in qemu/virtio-net:
> ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --do napi-set --json '{"id": 66, "threaded": 1}'
Is there a sane way for a 'real person' to set these from a normal
startup/network configuration script?
The netlink API is hardly user-friendly.
David
Powered by blists - more mailing lists