From: patchwork-bot+netdevbpf@kernel.org
To: fuyuanli <fuyuanli@didiglobal.com>
Cc: edumazet@google.com, rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] tcp: Add skb addr and sock addr to arguments of tracepoint tcp_probe.
Date: Fri, 08 Mar 2024 10:30:33 +0000 [thread overview]
Message-ID: <170989383394.12583.17811930111770070930.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240305030358.GA13138@didi-ThinkCentre-M920t-N000>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 5 Mar 2024 11:04:17 +0800 you wrote:
> It is useful to expose skb addr and sock addr to user in tracepoint
> tcp_probe, so that we can get more information while monitoring
> receiving of tcp data, by ebpf or other ways.
>
> For example, we need to identify a packet by seq and end_seq when
> calculate transmit latency between layer 2 and layer 4 by ebpf, but which is
> not available in tcp_probe, so we can only use kprobe hooking
> tcp_rcv_established to get them. But we can use tcp_probe directly if skb
> addr and sock addr are available, which is more efficient.
>
> [...]
Here is the summary with links:
- [net-next,v3] tcp: Add skb addr and sock addr to arguments of tracepoint tcp_probe.
https://git.kernel.org/netdev/net-next/c/caabd859c41b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-08 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 3:04 [PATCH net-next v3] tcp: Add skb addr and sock addr to arguments of tracepoint tcp_probe fuyuanli
2024-03-08 10:30 ` patchwork-bot+netdevbpf [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=170989383394.12583.17811930111770070930.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=edumazet@google.com \
--cc=fuyuanli@didiglobal.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=rostedt@goodmis.org \
/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).