From: patchwork-bot+netdevbpf@kernel.org
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: ronak.doshi@broadcom.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, bcm-kernel-feedback-list@broadcom.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
da.anzani@gmail.com, sean@ashe.io, mproche@gmail.com,
chjohnst@gmail.com
Subject: Re: [PATCH v2] vmxnet3: Suppress page allocation warning for massive Rx Data ring
Date: Sat, 28 Feb 2026 02:50:13 +0000 [thread overview]
Message-ID: <177224701379.2846847.10608754934612408646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260226163121.4045808-1-atomlin@atomlin.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Feb 2026 11:31:21 -0500 you wrote:
> The vmxnet3 driver supports an Rx Data ring (rx-mini) to optimise the
> processing of small packets. The size of this ring's DMA-coherent memory
> allocation is determined by the product of the primary Rx ring size and
> the data ring descriptor size:
>
> sz = rq->rx_ring[0].size * rq->data_ring.desc_size;
>
> [...]
Here is the summary with links:
- [v2] vmxnet3: Suppress page allocation warning for massive Rx Data ring
https://git.kernel.org/netdev/net-next/c/c31770c49348
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:[~2026-02-28 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 16:31 [PATCH v2] vmxnet3: Suppress page allocation warning for massive Rx Data ring Aaron Tomlin
2026-02-28 2: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=177224701379.2846847.10608754934612408646.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=atomlin@atomlin.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chjohnst@gmail.com \
--cc=da.anzani@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mproche@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ronak.doshi@broadcom.com \
--cc=sean@ashe.io \
/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