From: Lorenzo Bianconi <lorenzo@kernel•org>
To: Jakub Kicinski <kuba@kernel•org>
Cc: netdev@vger•kernel.org, bpf@vger•kernel.org, davem@davemloft•net,
pabeni@redhat•com, edumazet@google•com, hawk@kernel•org,
toke@redhat•com, memxor@gmail•com, alardam@gmail•com,
lorenzo.bianconi@redhat•com
Subject: Re: [RFC net-next] ethtool: provide XDP information with XDP_FEATURES_GET
Date: Mon, 6 Mar 2023 19:32:02 +0100 [thread overview]
Message-ID: <ZAYxolxpBtGZbO6m@lore-desk> (raw)
In-Reply-To: <20230306102150.5fee8042@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
> On Mon, 6 Mar 2023 11:26:10 +0100 Lorenzo Bianconi wrote:
> > Implement XDP_FEATURES_GET request to get network device information
> > about supported xdp functionalities through ethtool.
>
> You need to explain why. This is duplicating uAPI.
Hi Jakub,
So far the only way to dump the XDP features supported by the NIC is through
libbpf running bpf_xdp_query(). I would say it is handy for a sysadmin to
examine the XDP NIC capabilities in a similar way he/she is currently doing
for the hw offload capabilities. Something like (I have an ethtool user-space
patch not posted yet):
$ethtool --get-xdp-features eth0
XDP features for eth0:
xdp-basic: supported
xdp-redirect: supported
xdp-ndo-xmit: supported
xdp-xsk-zerocopy: not-supported
xdp-hw-offload: not-supported
xdp-rx-sg: not-supported
xdp-ndo-xmit-sg: not-supported
Regards,
Lorenzo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-06 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 10:26 [RFC net-next] ethtool: provide XDP information with XDP_FEATURES_GET Lorenzo Bianconi
2023-03-06 13:20 ` Simon Horman
2023-03-06 13:27 ` Lorenzo Bianconi
2023-03-06 18:21 ` Jakub Kicinski
2023-03-06 18:32 ` Lorenzo Bianconi [this message]
2023-03-06 19:32 ` Jakub Kicinski
2023-03-07 0:15 ` Lorenzo Bianconi
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=ZAYxolxpBtGZbO6m@lore-desk \
--to=lorenzo@kernel$(echo .)org \
--cc=alardam@gmail$(echo .)com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=lorenzo.bianconi@redhat$(echo .)com \
--cc=memxor@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=toke@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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