From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: <andrew@lunn.ch>, <davem@davemloft.net>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] tsnep: Link queues to NAPIs
Date: Mon, 13 Jan 2025 13:24:29 +0100 [thread overview]
Message-ID: <e986dc62-dea7-49f9-b65f-cd7e994c8e00@intel.com> (raw)
In-Reply-To: <20250110223939.37490-1-gerhard@engleder-embedded.com>
From: Gerhard Engleder <gerhard@engleder-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@engleder-embedded.com>
Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
Thanks,
Olek
next prev parent reply other threads:[~2025-01-13 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 22:39 [PATCH net-next] tsnep: Link queues to NAPIs Gerhard Engleder
2025-01-13 12:24 ` Alexander Lobakin [this message]
2025-01-13 19:59 ` Joe Damato
2025-01-13 20:32 ` Gerhard Engleder
2025-01-13 21:48 ` Joe Damato
2025-01-13 21:56 ` Jakub Kicinski
2025-01-13 22:20 ` Joe Damato
2025-01-13 22:31 ` Jakub Kicinski
2025-01-13 22:36 ` Joe Damato
2025-01-14 20:58 ` Gerhard Engleder
2025-01-14 21:22 ` Jakub Kicinski
2025-01-14 23:00 ` patchwork-bot+netdevbpf
2025-01-14 23:05 ` Joe Damato
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=e986dc62-dea7-49f9-b65f-cd7e994c8e00@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).