From: Jakub Kicinski <kuba@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Ahern <dsahern@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Joe Damato <jdamato@fastly.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: yaml gen NL families support in iproute2?
Date: Mon, 28 Oct 2024 17:06:47 -0700 [thread overview]
Message-ID: <20241028170647.65357d64@kernel.org> (raw)
In-Reply-To: <20241028164055.3059fad4@hermes.local>
On Mon, 28 Oct 2024 16:40:55 -0700 Stephen Hemminger wrote:
> > I can only find this thread now:
> > https://lore.kernel.org/all/20240302193607.36d7a015@kernel.org/
> > Could be a misunderstanding, but either way, documenting an existing
> > tool seems like strictly less work than recreating it from scratch.
>
> Is the toolset willing to maintain the backward compatibility guarantees
> that iproute2 has now? Bpf support was an example of how not to do it.
The specs are UAPI.
The Python and CLI tooling are a very thin layer of code basically
converting between JSON and netlink using the specs, so by virtue
of specs being UAPI they should be fully backward compatible.
The C library is intended to be fully backward compatible, but right
now only supports static linking.
next prev parent reply other threads:[~2024-10-29 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 17:41 yaml gen NL families support in iproute2? Paolo Abeni
2024-10-17 18:36 ` David Ahern
2024-10-21 20:58 ` Joe Damato
2024-10-22 7:55 ` Paolo Abeni
2024-10-28 20:58 ` Jakub Kicinski
2024-10-28 21:29 ` David Ahern
2024-10-28 22:15 ` Jakub Kicinski
2024-10-28 23:40 ` Stephen Hemminger
2024-10-29 0:06 ` Jakub Kicinski [this message]
2024-10-29 0:43 ` Stephen Hemminger
2024-10-29 9:29 ` Paolo Abeni
2024-10-29 13:39 ` Jakub Kicinski
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=20241028170647.65357d64@kernel.org \
--to=kuba@kernel.org \
--cc=dsahern@kernel.org \
--cc=jdamato@fastly.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).