From: Jakub Kicinski <kuba@kernel.org>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH v2] net: cache for same cpu skb_attempt_defer_free
Date: Wed, 14 Feb 2024 08:49:59 -0800 [thread overview]
Message-ID: <20240214084959.26d9076a@kernel.org> (raw)
In-Reply-To: <d8948716-ed07-48ab-a933-671f1fc4ee58@gmail.com>
On Wed, 14 Feb 2024 16:37:41 +0000 Pavel Begunkov wrote:
> To draw some conclusion, do you suggest to change anything
> in the patch?
Yes, Eric's suggestion of __napi_kfree_skb() is correct.
prev parent reply other threads:[~2024-02-14 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 13:33 [PATCH v2] net: cache for same cpu skb_attempt_defer_free Pavel Begunkov
2024-02-13 13:53 ` Eric Dumazet
2024-02-13 14:07 ` Pavel Begunkov
2024-02-13 14:28 ` Eric Dumazet
2024-02-14 3:13 ` Jakub Kicinski
2024-02-14 16:37 ` Pavel Begunkov
2024-02-14 16:49 ` Jakub Kicinski [this message]
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=20240214084959.26d9076a@kernel.org \
--to=kuba@kernel.org \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--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).