From: Paolo Abeni <pabeni@redhat.com>
To: Breno Leitao <leitao@debian.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
kuniyu@amazon.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, yonghong.song@linux.dev,
song@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next] udp: Add tracepoint for udp_sendmsg()
Date: Thu, 17 Apr 2025 08:57:24 +0200 [thread overview]
Message-ID: <67a977bc-a4b9-4c8b-bf2f-9e9e6bb0811e@redhat.com> (raw)
In-Reply-To: <20250416-udp_sendmsg-v1-1-1a886b8733c2@debian.org>
On 4/16/25 9:23 PM, 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()")
Why is it needed? what would add on top of a plain perf probe, which
will be always available for such function with such argument, as the
function can't be inlined?
Thanks,
Paolo
next prev parent reply other threads:[~2025-04-17 6:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 19:23 [PATCH net-next] udp: Add tracepoint for udp_sendmsg() Breno Leitao
2025-04-16 19:34 ` Willem de Bruijn
2025-04-17 11:31 ` Breno Leitao
2025-04-17 13:38 ` Willem de Bruijn
2025-04-16 23:16 ` David Ahern
2025-04-17 11:42 ` Breno Leitao
2025-04-17 15:55 ` David Ahern
2025-04-17 16:00 ` Breno Leitao
2025-04-18 4:57 ` David Ahern
2025-04-18 12:33 ` Steven Rostedt
2025-04-18 14:47 ` Steven Rostedt
2025-04-17 6:57 ` Paolo Abeni [this message]
2025-04-17 11:34 ` Breno Leitao
2025-04-17 13:17 ` Paolo Abeni
2025-04-17 15:37 ` Song Liu
2025-04-17 15:48 ` Willem de Bruijn
2025-04-17 20:00 ` Song Liu
2025-04-18 14:49 ` Willem de Bruijn
2025-05-27 13:45 ` Breno Leitao
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=67a977bc-a4b9-4c8b-bf2f-9e9e6bb0811e@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=song@kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yonghong.song@linux.dev \
/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