From: Ivan Babrou <ivan@cloudflare.com>
To: Linux Kernel Network Developers <netdev@vger.kernel.org>
Cc: kernel-team <kernel-team@cloudflare.com>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Stacks leading into skb:kfree_skb
Date: Fri, 14 Jul 2023 15:13:06 -0700 [thread overview]
Message-ID: <CABWYdi00L+O30Q=Zah28QwZ_5RU-xcxLFUK2Zj08A8MrLk9jzg@mail.gmail.com> (raw)
As requested by Jakub Kicinski and David Ahern here:
* https://lore.kernel.org/netdev/20230713201427.2c50fc7b@kernel.org/
I made some aggregations for the stacks we see leading into
skb:kfree_skb endpoint. There's a lot of data that is not easily
digestible, so I lightly massaged the data and added flamegraphs in
addition to raw stack counts. Here's the gist link:
* https://gist.github.com/bobrik/0e57671c732d9b13ac49fed85a2b2290
Let me know if any other format works better for you. I have perf
script output stashed just in case.
As a reminder (also mentioned in the gist), we're on v6.1, which is
the latest LTS.
I can't explain the reasons for all the network paths we have, but our
kernel / network people are CC'd if you have any questions.
next reply other threads:[~2023-07-14 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 22:13 Ivan Babrou [this message]
2023-07-15 0:54 ` Stacks leading into skb:kfree_skb David Ahern
2023-07-18 22:33 ` Ivan Babrou
2023-07-18 22:43 ` David Ahern
2023-07-18 22:36 ` Jakub Kicinski
2023-07-19 3:10 ` Yan Zhai
2023-07-19 3:50 ` David Ahern
2023-07-19 13:18 ` Willem de Bruijn
2023-07-19 13:26 ` Eric Dumazet
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='CABWYdi00L+O30Q=Zah28QwZ_5RU-xcxLFUK2Zj08A8MrLk9jzg@mail.gmail.com' \
--to=ivan@cloudflare.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--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).