From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, justin.chen@broadcom.com,
vikas.gupta@broadcom.com, rajashekar.hudumula@broadcom.com,
bhargava.marreddy@broadcom.com, arnd@arndb.de, markus@blochl.de,
hkallweit1@gmail.com, fmancera@suse.de,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, nb@tipi-net.de
Subject: Re: [PATCH net-next v2] net: bcmasp: Switch to page pool for RX path
Date: Thu, 09 Apr 2026 02:40:22 +0000 [thread overview]
Message-ID: <177570242254.964658.10910304956594603004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408001813.635679-1-florian.fainelli@broadcom.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Apr 2026 17:18:13 -0700 you wrote:
> This shows an improvement of 1.9% in reducing the CPU cycles and data
> cache misses.
>
> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
> ---
> Changes in v2:
>
> [...]
Here is the summary with links:
- [net-next,v2] net: bcmasp: Switch to page pool for RX path
https://git.kernel.org/netdev/net-next/c/686a7587bd0b
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-04-09 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 0:18 [PATCH net-next v2] net: bcmasp: Switch to page pool for RX path Florian Fainelli
2026-04-08 2:26 ` Justin Chen
2026-04-08 6:58 ` Nicolai Buchwitz
2026-04-09 2:40 ` 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=177570242254.964658.10910304956594603004.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=fmancera@suse.de \
--cc=hkallweit1@gmail.com \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@blochl.de \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rajashekar.hudumula@broadcom.com \
--cc=vikas.gupta@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.