From: patchwork-bot+netdevbpf@kernel.org
To: Arinzon@ci.codeaurora.org, David <darinzon@amazon.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
dwmw@amazon.com, zorik@amazon.com, matua@amazon.com,
saeedb@amazon.com, msw@amazon.com, aliguori@amazon.com,
nafea@amazon.com, alisaidi@amazon.com, benh@amazon.com,
akiyano@amazon.com, ndagan@amazon.com, shayagr@amazon.com,
itzko@amazon.com, osamaabb@amazon.com, amitbern@amazon.com
Subject: Re: [PATCH v1 net-next] net: ena: Add dynamic recycling mechanism for rx buffers
Date: Fri, 16 Jun 2023 05:50:20 +0000 [thread overview]
Message-ID: <168689462062.26047.642728221186195773.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230612121448.28829-1-darinzon@amazon.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Jun 2023 12:14:48 +0000 you wrote:
> From: David Arinzon <darinzon@amazon.com>
>
> The current implementation allocates page-sized rx buffers.
> As traffic may consist of different types and sizes of packets,
> in various cases, buffers are not fully used.
>
> This change (Dynamic RX Buffers - DRB) uses part of the allocated rx
> page needed for the incoming packet, and returns the rest of the
> unused page to be used again as an rx buffer for future packets.
> A threshold of 2K for unused space has been set in order to declare
> whether the remainder of the page can be reused again as an rx buffer.
>
> [...]
Here is the summary with links:
- [v1,net-next] net: ena: Add dynamic recycling mechanism for rx buffers
https://git.kernel.org/netdev/net-next/c/f7d625adeb7b
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:[~2023-06-16 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 12:14 [PATCH v1 net-next] net: ena: Add dynamic recycling mechanism for rx buffers darinzon
2023-06-16 5:50 ` 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=168689462062.26047.642728221186195773.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Arinzon@ci.codeaurora.org \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=amitbern@amazon.com \
--cc=benh@amazon.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=itzko@amazon.com \
--cc=kuba@kernel.org \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=osamaabb@amazon.com \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.com \
--cc=zorik@amazon.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).