From: Ratheesh Kannoth <rkannoth@marvell.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: <edumazet@google.com>, <mhiramat@kernel.org>,
<mathieu.desnoyers@efficios.com>, <rostedt@goodmis.org>,
<kuba@kernel.org>, <pabeni@redhat.com>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <linux-trace-kernel@vger.kernel.org>,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next 1/2] trace: adjust TP_STORE_ADDR_PORTS_SKB() parameters
Date: Mon, 11 Mar 2024 08:53:41 +0530 [thread overview]
Message-ID: <20240311032341.GA1241282@maili.marvell.com> (raw)
In-Reply-To: <20240311024104.67522-2-kerneljasonxing@gmail.com>
On 2024-03-11 at 08:11:03, Jason Xing (kerneljasonxing@gmail.com) wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> Introducing entry_saddr and entry_daddr parameters in this macro
> for later use can help us record the reverse 4-turple by analyzing
Did you mean tuple ? what is turple ?
> the 4-turple of the incoming skb when receiving.
>
> Signed-off-by: Jason Xing <kernelxing@tencent.com>
> ---
> include/trace/events/tcp.h | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
>
> diff --git a/include/trace/events/tcp.h b/include/trace/events/tcp.h
> index 699dafd204ea..2495a1d579be 100644
> --- a/include/trace/events/tcp.h
> +++ b/include/trace/events/tcp.h
> @@ -302,15 +302,15 @@ TRACE_EVENT(tcp_probe,
> __entry->skbaddr, __entry->skaddr)
> );
next prev parent reply other threads:[~2024-03-11 3:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 2:41 [PATCH net-next 0/2] tcp: make trace of reset logic complete Jason Xing
2024-03-11 2:41 ` [PATCH net-next 1/2] trace: adjust TP_STORE_ADDR_PORTS_SKB() parameters Jason Xing
2024-03-11 3:23 ` Ratheesh Kannoth [this message]
2024-03-11 3:28 ` Jason Xing
2024-03-11 2:41 ` [PATCH net-next 2/2] trace: tcp: fully support trace_tcp_send_reset Jason Xing
2024-03-11 3:27 ` Ratheesh Kannoth
2024-03-11 5:00 ` Jason Xing
2024-03-11 5:09 ` Ratheesh Kannoth
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=20240311032341.GA1241282@maili.marvell.com \
--to=rkannoth@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@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 \
/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).