[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z6UCELdW86ZdcTK4@LQ3V64L9R2>
Date: Thu, 6 Feb 2025 10:40:16 -0800
From: Joe Damato <jdamato@...tly.com>
To: David Laight <david.laight.linux@...il.com>
Cc: Samiullah Khawaja <skhawaja@...gle.com>,
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, Feb 05, 2025 at 11:10:03PM +0000, David Laight wrote:
> 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.
There is a C library, libynl that abstracts a lot of the netlink
stuff away and is quite nice. That said, if you wanted to use it
from a script, you'd probably need bindings for it in the language
of your choice.
If you meant more a shell script type setup, then yea.... the python
CLI is (AFAIK) the only option.
Powered by blists - more mailing lists