[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e986dc62-dea7-49f9-b65f-cd7e994c8e00@intel.com>
Date: Mon, 13 Jan 2025 13:24:29 +0100
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Gerhard Engleder <gerhard@...leder-embedded.com>
CC: <andrew@...n.ch>, <davem@...emloft.net>, <edumazet@...gle.com>,
<kuba@...nel.org>, <pabeni@...hat.com>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] tsnep: Link queues to NAPIs
From: Gerhard Engleder <gerhard@...leder-embedded.com>
Date: Fri, 10 Jan 2025 23:39:39 +0100
> Use netif_queue_set_napi() to link queues to NAPI instances so that they
> can be queried with netlink.
>
> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --dump queue-get --json='{"ifindex": 11}'
> [{'id': 0, 'ifindex': 11, 'napi-id': 9, 'type': 'rx'},
> {'id': 1, 'ifindex': 11, 'napi-id': 10, 'type': 'rx'},
> {'id': 0, 'ifindex': 11, 'napi-id': 9, 'type': 'tx'},
> {'id': 1, 'ifindex': 11, 'napi-id': 10, 'type': 'tx'}]
>
> Additionally use netif_napi_set_irq() to also provide NAPI interrupt
> number to userspace.
>
> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --do napi-get --json='{"id": 9}'
> {'defer-hard-irqs': 0,
> 'gro-flush-timeout': 0,
> 'id': 9,
> 'ifindex': 11,
> 'irq': 42,
> 'irq-suspend-timeout': 0}
>
> Providing information about queues to userspace makes sense as APIs like
> XSK provide queue specific access. Also XSK busy polling relies on
> queues linked to NAPIs.
>
> Signed-off-by: Gerhard Engleder <gerhard@...leder-embedded.com>
Reviewed-by: Alexander Lobakin <aleksander.lobakin@...el.com>
Thanks,
Olek
Powered by blists - more mailing lists