From: Oscar Maes <oscmaes92@gmail.com>
To: netdev@vger.kernel.org
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
Oscar Maes <oscmaes92@gmail.com>
Subject: [PATCH net-next 0/2] pcnet32: switch to napi_alloc_skb() and napi_gro_receive()
Date: Wed, 20 May 2026 08:33:27 +0200 [thread overview]
Message-ID: <20260520063329.6387-1-oscmaes92@gmail.com> (raw)
Use the newer and more efficient napi_alloc_skb() and napi_gro_receive()
APIs to improve RX throughput.
In my testing this resulted in up to a 25% RX throughput increase in iperf3
tests in both directions.
Oscar Maes (2):
pcnet32: stop holding device spin lock during napi_complete_done
pcnet32: switch to napi_alloc_skb() and napi_gro_receive()
drivers/net/ethernet/amd/pcnet32.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
2.39.5
next reply other threads:[~2026-05-20 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 6:33 Oscar Maes [this message]
2026-05-20 6:33 ` [PATCH net-next 1/2] pcnet32: stop holding device spin lock during napi_complete_done Oscar Maes
2026-05-20 12:12 ` Andrew Lunn
2026-05-20 6:33 ` [PATCH net-next 2/2] pcnet32: switch to napi_alloc_skb() and napi_gro_receive() Oscar Maes
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=20260520063329.6387-1-oscmaes92@gmail.com \
--to=oscmaes92@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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