[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6800064ea440f_fc9d7294c4@willemb.c.googlers.com.notmuch>
Date: Wed, 16 Apr 2025 15:34:38 -0400
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Breno Leitao <leitao@...ian.org>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
"David S. Miller" <davem@...emloft.net>,
David Ahern <dsahern@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
kuniyu@...zon.com
Cc: netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
yonghong.song@...ux.dev,
song@...nel.org,
kernel-team@...a.com,
Breno Leitao <leitao@...ian.org>
Subject: Re: [PATCH net-next] udp: Add tracepoint for udp_sendmsg()
Breno Leitao wrote:
> Add a lightweight tracepoint to monitor UDP send message operations,
> similar to the recently introduced tcp_sendmsg_locked() trace event in
> commit 0f08335ade712 ("trace: tcp: Add tracepoint for
> tcp_sendmsg_locked()")
>
> This implementation uses DECLARE_TRACE instead of TRACE_EVENT to avoid
> creating extensive trace event infrastructure and exporting to tracefs,
> keeping it minimal and efficient.
>
> Since this patch creates a rawtracepoint, it can be accessed using
> standard tracing tools like bpftrace:
>
> rawtracepoint:udp_sendmsg_tp {
> ...
> }
What does this enable beyond kfunc:udp_sendmsg?
The arguments are the same, unlike the TCP tracepoint.
Powered by blists - more mailing lists