[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210723075931.722b859f@hermes.local>
Date: Fri, 23 Jul 2021 07:59:31 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Justin Iurman <justin.iurman@...ege.be>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH iproute2-next 1/3] Add, show, link, remove IOAM
namespaces and schemas
On Fri, 23 Jul 2021 16:48:00 +0200
Justin Iurman <justin.iurman@...ege.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@...ege.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
Powered by blists - more mailing lists