From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsahern@gmail.com>
Cc: Justin Iurman <justin.iurman@uliege.be>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2 1/3] Add, show, link, remove IOAM namespaces and schemas
Date: Tue, 10 Aug 2021 20:47:53 -0700 [thread overview]
Message-ID: <20210810204753.546c151d@hermes.local> (raw)
In-Reply-To: <dbec63c4-8d05-b476-f508-b43eac749810@gmail.com>
On Fri, 30 Jul 2021 08:39:50 -0600
David Ahern <dsahern@gmail.com> wrote:
> On 7/29/21 10:41 AM, Justin Iurman wrote:
> > I see. But, in that case, I'm wondering if it wouldn't be better to directly modify "matches" internally so that we keep consistency between modules without changing everything.
> >
> > Thoughts?
>
> matches() can not be changed.
>
> iproute_lwtunnel code uses full strcmp. The new ioam command can start
> off the same way.
Agreed.
Although "ip l s" is cool to impress people it is a maintenance nightmare
as more things get added.
next prev parent reply other threads:[~2021-08-11 3:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 17:21 [PATCH iproute2-next v2 0/3] Provide support for IOAM Justin Iurman
2021-07-24 17:21 ` [PATCH iproute2-next v2 1/3] Add, show, link, remove IOAM namespaces and schemas Justin Iurman
2021-07-29 2:41 ` David Ahern
2021-07-29 9:51 ` Justin Iurman
2021-07-29 14:32 ` David Ahern
2021-07-29 16:41 ` Justin Iurman
2021-07-30 14:39 ` David Ahern
2021-08-11 3:47 ` Stephen Hemminger [this message]
2021-08-11 3:46 ` Stephen Hemminger
2021-07-24 17:21 ` [PATCH iproute2-next v2 2/3] New IOAM6 encap type for routes Justin Iurman
2021-07-27 13:42 ` Justin Iurman
2021-07-29 2:44 ` David Ahern
2021-07-24 17:21 ` [PATCH iproute2-next v2 3/3] IOAM man8 Justin Iurman
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=20210810204753.546c151d@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=justin.iurman@uliege.be \
--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;
as well as URLs for NNTP newsgroup(s).