[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250402120149.4ca403b1@gandalf.local.home>
Date: Wed, 2 Apr 2025 12:01:49 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: David Ahern <dsahern@...nel.org>
Cc: Breno Leitao <leitao@...ian.org>, Eric Dumazet <edumazet@...gle.com>,
Neal Cardwell <ncardwell@...gle.com>, Kuniyuki Iwashima
<kuniyu@...zon.com>, Masami Hiramatsu <mhiramat@...nel.org>, Mathieu
Desnoyers <mathieu.desnoyers@...icios.com>, "David S. Miller"
<davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, kernel-team@...a.com,
yonghong.song@...ux.dev
Subject: Re: [PATCH net-next] trace: tcp: Add tracepoint for tcp_sendmsg()
On Wed, 2 Apr 2025 08:11:03 -0600
David Ahern <dsahern@...nel.org> wrote:
> How about passing in the sk reference here; not needed for trace
> entries, but makes it directly accessible for bpf programs.
Not to mention event probes (dynamic trace events that can be attached to
existing events and the fields can be dereferenced). One day I'll add
documentation about event probes as they have been in the kernel since 5.15! :-p
-- Steve
Powered by blists - more mailing lists