From: Stephen Hemminger <stephen@networkplumber.org>
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 1/3] Add, show, link, remove IOAM namespaces and schemas
Date: Fri, 23 Jul 2021 07:59:31 -0700 [thread overview]
Message-ID: <20210723075931.722b859f@hermes.local> (raw)
In-Reply-To: <20210723144802.14380-2-justin.iurman@uliege.be>
On Fri, 23 Jul 2021 16:48:00 +0200
Justin Iurman <justin.iurman@uliege.be> wrote:
> This patch provides support for adding, listing and removing IOAM namespaces
> and schemas with iproute2. When adding an IOAM namespace, both "data" (=u32)
> and "wide" (=u64) are optional. Therefore, you can either have none, one of
> them, or both at the same time. When adding an IOAM schema, there is no
> restriction on "DATA" except its size (see IOAM6_MAX_SCHEMA_DATA_LEN). By
> default, an IOAM namespace has no active IOAM schema (meaning an IOAM namespace
> is not linked to an IOAM schema), and an IOAM schema is not considered
> as "active" (meaning an IOAM schema is not linked to an IOAM namespace). It is
> possible to link an IOAM namespace with an IOAM schema, thanks to the last
> command below (meaning the IOAM schema will be considered as "active" for the
> specific IOAM namespace).
>
> $ ip ioam
> Usage: ip ioam { COMMAND | help }
> ip ioam namespace show
> ip ioam namespace add ID [ data DATA32 ] [ wide DATA64 ]
> ip ioam namespace del ID
> ip ioam schema show
> ip ioam schema add ID DATA
> ip ioam schema del ID
> ip ioam namespace set ID schema { ID | none }
>
> Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
> ---
> include/uapi/linux/ioam6_genl.h | 52 +++++
> ip/Makefile | 2 +-
> ip/ip.c | 3 +-
> ip/ip_common.h | 1 +
> ip/ipioam6.c | 351 ++++++++++++++++++++++++++++++++
> 5 files changed, 407 insertions(+), 2 deletions(-)
> create mode 100644 include/uapi/linux/ioam6_genl.h
> create mode 100644 ip/ipioam6.c
Please update the man pages as well
next prev parent reply other threads:[~2021-07-23 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 14:47 [PATCH iproute2-next 0/3] Provide support for IOAM Justin Iurman
2021-07-23 14:48 ` [PATCH iproute2-next 1/3] Add, show, link, remove IOAM namespaces and schemas Justin Iurman
2021-07-23 14:58 ` Stephen Hemminger
2021-07-23 15:07 ` Justin Iurman
2021-07-23 14:59 ` Stephen Hemminger [this message]
2021-07-23 15:00 ` Stephen Hemminger
2021-07-23 14:48 ` [PATCH iproute2-next 2/3] New IOAM6 encap type for routes Justin Iurman
2021-07-23 14:48 ` [PATCH iproute2-next 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=20210723075931.722b859f@hermes.local \
--to=stephen@networkplumber.org \
--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).