From: Breno Leitao <leitao@debian.org>
To: David Ahern <dsahern@kernel.org>
Cc: 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>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
kuniyu@amazon.com, 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 04:42:25 -0700 [thread overview]
Message-ID: <aADpIftw30HBT8pq@gmail.com> (raw)
In-Reply-To: <4dd9504c-4bce-4acd-874c-8eed8c311a2f@kernel.org>
Hello David,
On Wed, Apr 16, 2025 at 04:16:26PM -0700, David Ahern wrote:
> On 4/16/25 1:23 PM, Breno Leitao wrote:
> > diff --git a/net/ipv4/udp.c b/net/ipv4/udp.c
> > index f9f5b92cf4b61..8c2902504a399 100644
> > --- a/net/ipv4/udp.c
> > +++ b/net/ipv4/udp.c
> > @@ -1345,6 +1345,8 @@ int udp_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
> > connected = 1;
> > }
> >
> > + trace_udp_sendmsg_tp(sk, msg);
>
> why `_tp` suffix? the usual naming is trace_${func}
I got the impression that DECLARE_TRACE() raw tracepoints names end up
in _tp():
include/trace/events/tcp.h
DECLARE_TRACE(tcp_cwnd_reduction_tp,
include/trace/events/sched.h
DECLARE_TRACE(pelt_cfs_tp,
DECLARE_TRACE(pelt_rt_tp,
DECLARE_TRACE(pelt_dl_tp,
DECLARE_TRACE(pelt_hw_tp,
DECLARE_TRACE(pelt_irq_tp,
DECLARE_TRACE(pelt_se_tp,
DECLARE_TRACE(sched_cpu_capacity_tp,
DECLARE_TRACE(sched_overutilized_tp,
DECLARE_TRACE(sched_util_est_cfs_tp,
DECLARE_TRACE(sched_util_est_se_tp,
DECLARE_TRACE(sched_update_nr_running_tp,
DECLARE_TRACE(sched_compute_energy_tp,
DECLARE_TRACE(sched_entry_tp,
DECLARE_TRACE(sched_exit_tp,
But, I am happy to remove _tp if that is not correct.
Thanks,
--breno
next prev parent reply other threads:[~2025-04-17 11:42 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 [this message]
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
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=aADpIftw30HBT8pq@gmail.com \
--to=leitao@debian.org \
--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=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=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).