From: Jakub Kicinski <kuba@kernel.org>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: vxlan: how to expose opt-in RFC conformity with unprocessed header flags
Date: Tue, 16 Jan 2024 08:23:57 -0800 [thread overview]
Message-ID: <20240116082357.22daf549@kernel.org> (raw)
In-Reply-To: <db8b9e19-ad75-44d3-bfb2-46590d426ff5@proxmox.com>
On Fri, 12 Jan 2024 16:13:22 +0100 Thomas Lamprecht wrote:
> What would be the accepted way to add a switch of making this RFC conform in
> an opt-in way? A module parameter? A sysfs entry? Through netlink?
Thru netlink. My intuition would be to try to add a "ignore
bits" mask, rather than "RFC compliance knob" because RFCs
may have shorter lifespan than kernel's uAPI guarantees..
next prev parent reply other threads:[~2024-01-16 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 15:13 vxlan: how to expose opt-in RFC conformity with unprocessed header flags Thomas Lamprecht
2024-01-16 16:23 ` Jakub Kicinski [this message]
2024-01-22 9:39 ` Ido Schimmel
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=20240116082357.22daf549@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=t.lamprecht@proxmox.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).