Received-SPF: pass (google.com: domain of linux-kernel+bounces-96830-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next v3] tcp: Add skb addr and sock addr to arguments of
 tracepoint tcp_probe.
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <170989383394.12583.17811930111770070930.git-patchwork-notify@kernel.org>
Date: Fri, 08 Mar 2024 10:30:33 +0000
References: <20240305030358.GA13138@didi-ThinkCentre-M920t-N000>
In-Reply-To: <20240305030358.GA13138@didi-ThinkCentre-M920t-N000>
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

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