From: Paolo Abeni <pabeni@redhat.com>
To: Justin Iurman <justin.iurman@uliege.be>, netdev@vger.kernel.org
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/2] net: ipv6: ioam6: new feature tunsrc
Date: Thu, 22 Aug 2024 10:44:43 +0200 [thread overview]
Message-ID: <e15e5b9e-e392-4cf4-8620-9bcc375711b1@redhat.com> (raw)
In-Reply-To: <20240817131818.11834-3-justin.iurman@uliege.be>
On 8/17/24 15:18, Justin Iurman wrote:
> This patch provides a new feature (i.e., "tunsrc") for the tunnel (i.e.,
> "encap") mode of ioam6. Just like seg6 already does, except it is
> attached to a route. The "tunsrc" is optional: when not provided (by
> default), the automatic resolution is applied. Using "tunsrc" when
> possible has a benefit: performance. See the comparison:
> - before (= "encap" mode): https://ibb.co/bNCzvf7
> - after (= "encap" mode with "tunsrc"): https://ibb.co/PT8L6yq
Please note that Jakub's question about self-tests still stands off.
I think the easier path for that goal is to have this patch merged, and
than the iproute counter-part, and finally adds the related functional
tests (you will need to probe the kernel and iproute features), but
please follow-up on that, thanks!
Paolo
next prev parent reply other threads:[~2024-08-22 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 13:18 [PATCH net-next v3 0/2] net: ipv6: ioam6: introduce tunsrc Justin Iurman
2024-08-17 13:18 ` [PATCH net-next v3 1/2] net: ipv6: ioam6: code alignment Justin Iurman
2024-08-17 13:18 ` [PATCH net-next v3 2/2] net: ipv6: ioam6: new feature tunsrc Justin Iurman
2024-08-22 8:44 ` Paolo Abeni [this message]
2024-08-22 12:46 ` Justin Iurman
2024-08-22 9:00 ` [PATCH net-next v3 0/2] net: ipv6: ioam6: introduce tunsrc patchwork-bot+netdevbpf
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=e15e5b9e-e392-4cf4-8620-9bcc375711b1@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®