From: "Yeounsu Moon" <yyyynoom@gmail.com>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: "Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] net: dlink: count dropped packets on skb allocation failure
Date: Fri, 12 Sep 2025 19:03:46 +0900 [thread overview]
Message-ID: <DCQQIQ5STYSJ.1X531TK8K9OTS@gmail.com> (raw)
In-Reply-To: <20250911170815.006b3a31@kernel.org>
On Fri Sep 12, 2025 at 9:08 AM KST, Jakub Kicinski wrote:
> On Wed, 10 Sep 2025 14:48:37 +0900 Yeounsu Moon wrote:
>> Track dropped packet statistics when skb allocation fails
>> in the receive path.
>
> I'm not sure that failing to allocate a buffer results in dropping
> one packet in this driver. The statistics have specific meaning, if
> you're just trying to use dropped to mean "buffer allocation failures"
> that's not allowed. If I'm misreading the code please explain in more
> detail in the commit message and repost.
>
I think you understand the code better than I do.
Your insights are always surprising to me.
I believed that when `netdev_alloc_skb()` fails, it leads to dropping packets.
I also found many cases where `rx_dropped` was incremented when
`netdev_alloc_skb()` failed.
However, I'm not entirely sure whether such a failure actually results
in a misisng packet. I'll resend the patch after verifying whether the packet
is really dropped.
Thank you for reviewing!
Yeounsu Moon
next prev parent reply other threads:[~2025-09-12 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 5:48 [PATCH net-next] net: dlink: count dropped packets on skb allocation failure Yeounsu Moon
2025-09-11 17:02 ` Simon Horman
2025-09-12 9:27 ` Yeounsu Moon
2025-09-12 0:08 ` Jakub Kicinski
2025-09-12 10:03 ` Yeounsu Moon [this message]
2025-09-12 14:35 ` 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=DCQQIQ5STYSJ.1X531TK8K9OTS@gmail.com \
--to=yyyynoom@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).