From: patchwork-bot+netdevbpf@kernel.org
To: Sieng-Piaw Liew <liew.s.piaw@gmail.com>
Cc: chris.snook@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: ag71xx: switch to napi_build_skb() to reuse skbuff_heads
Date: Fri, 08 Jul 2022 13:30:14 +0000 [thread overview]
Message-ID: <165728701439.7845.10823920521689241514.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220707141056.2644-1-liew.s.piaw@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 7 Jul 2022 22:10:56 +0800 you wrote:
> napi_build_skb() reuses NAPI skbuff_head cache in order to save some
> cycles on freeing/allocating skbuff_heads on every new Rx or completed
> Tx.
> Use napi_consume_skb() to feed the cache with skbuff_heads of completed
> Tx, so it's never empty. The budget parameter is added to indicate NAPI
> context, as a value of zero can be passed in the case of netpoll.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: ag71xx: switch to napi_build_skb() to reuse skbuff_heads
https://git.kernel.org/netdev/net-next/c/67d7ebdeb2d5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-07-08 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 0:44 [PATCH] net: ag71xx: switch to napi_build_skb() to reuse skbuff_heads Sieng-Piaw Liew
2022-07-07 2:52 ` Jakub Kicinski
2022-07-07 14:10 ` [PATCH net-next v2] " Sieng-Piaw Liew
2022-07-08 13:30 ` patchwork-bot+netdevbpf [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=165728701439.7845.10823920521689241514.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=liew.s.piaw@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).