From: patchwork-bot+netdevbpf@kernel.org
To: Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
quic_jzenner@quicinc.com, cong.wang@bytedance.com,
qitao.xu@bytedance.com, bigeasy@linutronix.de,
rostedt@goodmis.org, mingo@redhat.com, quic_stranche@quicinc.com
Subject: Re: [PATCH net-next v2] net: Print hashed skb addresses for all net and qdisc events
Date: Mon, 27 Jun 2022 11:00:18 +0000 [thread overview]
Message-ID: <165632761825.13770.14445875022543413232.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1656106465-26544-1-git-send-email-quic_subashab@quicinc.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 24 Jun 2022 15:34:25 -0600 you wrote:
> The following commits added support for printing the real address-
> 65875073eddd ("net: use %px to print skb address in trace_netif_receive_skb")
> 70713dddf3d2 ("net_sched: introduce tracepoint trace_qdisc_enqueue()")
> 851f36e40962 ("net_sched: use %px to print skb address in trace_qdisc_dequeue()")
>
> However, tracing the packet traversal shows a mix of hashes and real
> addresses. Pasting a sample trace for reference-
>
> [...]
Here is the summary with links:
- [net-next,v2] net: Print hashed skb addresses for all net and qdisc events
https://git.kernel.org/netdev/net-next/c/6deb209dc6b0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-06-27 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 21:34 [PATCH net-next v2] net: Print hashed skb addresses for all net and qdisc events Subash Abhinov Kasiviswanathan
2022-06-27 11:00 ` patchwork-bot+netdevbpf [this message]
2022-06-27 19:36 ` Cong Wang
2022-06-27 19:49 ` Subash Abhinov Kasiviswanathan (KS)
2022-07-03 4:36 ` Cong Wang
2022-07-08 20:18 ` Steven Rostedt
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=165632761825.13770.14445875022543413232.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qitao.xu@bytedance.com \
--cc=quic_jzenner@quicinc.com \
--cc=quic_stranche@quicinc.com \
--cc=quic_subashab@quicinc.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