From: Daniel Borkmann <daniel@iogearbox.net>
To: martin.lau@linux.dev
Cc: razor@blackwall.org, pabeni@redhat.com, bpf@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH bpf-next 2/3] netkit: Add add netkit {head,tail}room to rt_link.yaml
Date: Thu, 19 Dec 2024 18:39:27 +0100 [thread overview]
Message-ID: <20241219173928.464437-2-daniel@iogearbox.net> (raw)
In-Reply-To: <20241219173928.464437-1-daniel@iogearbox.net>
Add netkit {head,tail}room attribute support to the rt_link.yaml spec file.
Example:
# ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/rt_link.yaml \
--do getlink --json '{"ifname": "nk0"}' --output-json | jq
[...]
"linkinfo": {
"kind": "netkit",
"data": {
}
},
[...]
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Cc: Nikolay Aleksandrov <razor@blackwall.org>
---
Documentation/netlink/specs/rt_link.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/netlink/specs/rt_link.yaml b/Documentation/netlink/specs/rt_link.yaml
index 9ffa13b77dcf..dbeae6b1c548 100644
--- a/Documentation/netlink/specs/rt_link.yaml
+++ b/Documentation/netlink/specs/rt_link.yaml
@@ -2166,6 +2166,12 @@ attribute-sets:
name: peer-scrub
type: u32
enum: netkit-scrub
+ -
+ name: headroom
+ type: u16
+ -
+ name: tailroom
+ type: u16
sub-messages:
-
--
2.43.0
next prev parent reply other threads:[~2024-12-19 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 17:39 [PATCH bpf-next 1/3] netkit: Allow for configuring needed_{head,tail}room Daniel Borkmann
2024-12-19 17:39 ` Daniel Borkmann [this message]
2024-12-21 7:22 ` [PATCH bpf-next 2/3] netkit: Add add netkit {head,tail}room to rt_link.yaml Nikolay Aleksandrov
2024-12-19 17:39 ` [PATCH bpf-next 3/3] selftests/bpf: Extend netkit tests to validate set {head,tail}room Daniel Borkmann
2024-12-21 7:22 ` Nikolay Aleksandrov
2024-12-20 2:23 ` [PATCH bpf-next 1/3] netkit: Allow for configuring needed_{head,tail}room Jakub Kicinski
2024-12-20 9:06 ` Daniel Borkmann
2024-12-21 0:04 ` Daniel Borkmann
2024-12-21 7:22 ` Nikolay Aleksandrov
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=20241219173928.464437-2-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
/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