public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Justin Iurman <justin.iurman@uliege.be>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/3] ioam6: netlink multicast event
Date: Fri, 23 Feb 2024 09:50:38 -0700	[thread overview]
Message-ID: <fd7b788a-2e12-4828-8f5f-d17536ed5a10@kernel.org> (raw)
In-Reply-To: <20240223144135.12826-1-justin.iurman@uliege.be>

On 2/23/24 7:41 AM, Justin Iurman wrote:
> v4:
>  - rebase on top of net merge
> v3:
>  - patchset was mistakenly superseded due to same cover title used for
>    iproute2-next equivalent patch -> resend (renamed)
> v2:
>  - fix warnings
> 
> Add generic netlink multicast event support to ioam6 as another solution
> to share IOAM data with user space. The other one being via IPv6 raw
> sockets combined with ancillary data. This patchset focuses on the IOAM
> Pre-allocated Trace (the only Option-Type currently supported), and so
> on IOAM "trace" events. See an example of a consumer here [1].
> 
>   [1] https://github.com/Advanced-Observability/ioam-agent-python/blob/netlink_event/ioam-agent.py
> 
> Justin Iurman (3):
>   uapi: ioam6: API for netlink multicast events
>   net: ioam6: multicast event
>   net: exthdrs: ioam6: send trace event
> 
>  include/net/ioam6.h             |  4 +++
>  include/uapi/linux/ioam6_genl.h | 20 +++++++++++
>  net/ipv6/exthdrs.c              |  6 ++++
>  net/ipv6/ioam6.c                | 64 +++++++++++++++++++++++++++++++++
>  4 files changed, 94 insertions(+)
> 
> 
> base-commit: a818bd12538c1408c7480de31573cdb3c3c0926f

For the set:
Reviewed-by: David Ahern <dsahern@kernel.org>


      parent reply	other threads:[~2024-02-23 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 14:41 [PATCH net-next v4 0/3] ioam6: netlink multicast event Justin Iurman
2024-02-23 14:41 ` [PATCH net-next v4 1/3] uapi: ioam6: API for netlink multicast events Justin Iurman
2024-02-23 14:41 ` [PATCH net-next v4 2/3] net: ioam6: multicast event Justin Iurman
2024-02-23 14:41 ` [PATCH net-next v4 3/3] net: exthdrs: ioam6: send trace event Justin Iurman
2024-02-23 18:20   ` Justin Iurman
2024-02-23 16:50 ` David Ahern [this message]

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=fd7b788a-2e12-4828-8f5f-d17536ed5a10@kernel.org \
    --to=dsahern@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=justin.iurman@uliege.be \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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