From: Jakub Kicinski <kuba@kernel.org>
To: Lorenzo Bianconi <lorenzo@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 11:32:25 -0800 [thread overview]
Message-ID: <20230306113225.6a087a4c@kernel.org> (raw)
In-Reply-To: <ZAYxolxpBtGZbO6m@lore-desk>
On Mon, 6 Mar 2023 19:32:02 +0100 Lorenzo Bianconi wrote:
> 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):
The sysadmin running linux-next or 6.3-rc1, that is? :)
The plan in my head is to package a tool like tools/net/ynl/cli.py for
sysadmins to use. Either package it with the specs or expose the specs
in sysfs like we expose BTF and kheaders.
I was hoping we can "give it a release or two" to get more experience
with the specs with just developers using them, 'cause once sysadmins
are using them we'll have to worry about backward compat.
But I don't want to hold you back so if the plan above sounds sensible
to you we can start executing on it, perhaps?
Alternative would be to teach ethtool or some other tool (new tool?)
to speak netdev genl, because duplicating the uAPI at the kernel level
really seems odd :(
next prev parent reply other threads:[~2023-03-06 19: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
2023-03-06 19:32 ` Jakub Kicinski [this message]
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=20230306113225.6a087a4c@kernel.org \
--to=kuba@kernel.org \
--cc=alardam@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@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).