From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
amcohen@nvidia.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/7] mlxsw: Use page pool for Rx buffers allocation
Date: Thu, 20 Jun 2024 00:50:32 +0000 [thread overview]
Message-ID: <171884463260.1669.4829676069080394428.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1718709196.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Jun 2024 13:34:39 +0200 you wrote:
> Amit Cohen writes:
>
> After using NAPI to process events from hardware, the next step is to
> use page pool for Rx buffers allocation, which is also enhances
> performance.
>
> To simplify this change, first use page pool to allocate one continuous
> buffer for each packet, later memory consumption can be improved by using
> fragmented buffers.
>
> [...]
Here is the summary with links:
- [net-next,1/7] mlxsw: pci: Split NAPI setup/teardown into two steps
https://git.kernel.org/netdev/net-next/c/39fa294f580a
- [net-next,2/7] mlxsw: pci: Store CQ pointer as part of RDQ structure
https://git.kernel.org/netdev/net-next/c/7555b7f3385f
- [net-next,3/7] mlxsw: pci: Initialize page pool per CQ
https://git.kernel.org/netdev/net-next/c/5642c6a08693
- [net-next,4/7] mlxsw: pci: Use page pool for Rx buffers allocation
https://git.kernel.org/netdev/net-next/c/b5b60bb491b2
- [net-next,5/7] mlxsw: pci: Optimize data buffer access
https://git.kernel.org/netdev/net-next/c/0f3cd437a1d8
- [net-next,6/7] mlxsw: pci: Do not store SKB for RDQ elements
https://git.kernel.org/netdev/net-next/c/e8441b1f6b64
- [net-next,7/7] mlxsw: pci: Use napi_consume_skb() to free SKB as part of Tx completion
https://git.kernel.org/netdev/net-next/c/d94ae6415bec
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:[~2024-06-20 0:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 11:34 [PATCH net-next 0/7] mlxsw: Use page pool for Rx buffers allocation Petr Machata
2024-06-18 11:34 ` [PATCH net-next 1/7] mlxsw: pci: Split NAPI setup/teardown into two steps Petr Machata
2024-06-18 11:34 ` [PATCH net-next 2/7] mlxsw: pci: Store CQ pointer as part of RDQ structure Petr Machata
2024-06-18 11:34 ` [PATCH net-next 3/7] mlxsw: pci: Initialize page pool per CQ Petr Machata
2024-06-18 11:34 ` [PATCH net-next 4/7] mlxsw: pci: Use page pool for Rx buffers allocation Petr Machata
2024-06-18 11:34 ` [PATCH net-next 5/7] mlxsw: pci: Optimize data buffer access Petr Machata
2024-06-18 11:34 ` [PATCH net-next 6/7] mlxsw: pci: Do not store SKB for RDQ elements Petr Machata
2024-06-18 11:34 ` [PATCH net-next 7/7] mlxsw: pci: Use napi_consume_skb() to free SKB as part of Tx completion Petr Machata
2024-06-18 14:01 ` [PATCH net-next 0/7] mlxsw: Use page pool for Rx buffers allocation Jiri Pirko
2024-06-20 0: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=171884463260.1669.4829676069080394428.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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).