From: yajun.deng@linux.dev
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: davem@davemloft.net, rostedt@goodmis.org, mingo@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dev: introduce netdev_drop_inc()
Date: Wed, 09 Feb 2022 02:20:07 +0000 [thread overview]
Message-ID: <753bb02bfa8c2cf5c08c63c31f193f90@linux.dev> (raw)
In-Reply-To: <20220208162729.41b62ae7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
February 9, 2022 8:27 AM, "Jakub Kicinski" <kuba@kernel.org> wrote:
> On Tue, 8 Feb 2022 14:43:18 +0800 Yajun Deng wrote:
>
>> We will use 'sudo perf record -g -a -e skb:kfree_skb' command to trace
>> the dropped packets when dropped increase in the output of ifconfig.
>> But there are two cases, one is only called kfree_skb(), another is
>> increasing the dropped and called kfree_skb(). The latter is what
>> we need. So we need to separate these two cases.
>>
>> From the other side, the dropped packet came from the core network and
>> the driver, we also need to separate these two cases.
>>
>> Add netdev_drop_inc() and add a tracepoint for the core network dropped
>> packets. use 'sudo perf record -g -a -e net:netdev_drop' and 'sudo perf
>> script' will recored the dropped packets by the core network.
>>
>> Signed-off-by: Yajun Deng <yajun.deng@linux.dev>
>
> Have you seen the work that's being done around kfree_skb_reason()?
Yes, I saw it. The focus of kfree_skb_reason() is trace kfree_skb() and the reason,
but the focus of this patch only traces this case of the dropped packet.
I don't want to trace all kfree_skb(), but I just want to trace the dropped packet.
This command 'sudo perf record -g -a -e skb:kfree_skb' would trace all kfree_skb(),
kfree_skb() would drowned out the case of dropped packets when the samples were too large.
next prev parent reply other threads:[~2022-02-09 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 6:43 [PATCH net-next] net: dev: introduce netdev_drop_inc() Yajun Deng
2022-02-09 0:27 ` Jakub Kicinski
2022-02-09 2:20 ` yajun.deng [this message]
2022-02-09 3:53 ` Jakub Kicinski
2022-02-09 7:27 ` yajun.deng
2022-02-09 15:31 ` Jakub Kicinski
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=753bb02bfa8c2cf5c08c63c31f193f90@linux.dev \
--to=yajun.deng@linux.dev \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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).