public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
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 v2 0/2] pcnet32: switch to napi_alloc_skb() and napi_gro_receive()
Date: Mon, 25 May 2026 14:54:35 +0200	[thread overview]
Message-ID: <20260525125437.4061-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.

Changes in v2:
- Clarified why releasing the spinlock during napi_complete_done is legal

Previous version:
https://lore.kernel.org/netdev/20260520063329.6387-1-oscmaes92@gmail.com/

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


             reply	other threads:[~2026-05-25 12:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 12:54 Oscar Maes [this message]
2026-05-25 12:54 ` [PATCH net-next v2 1/2] pcnet32: stop holding device spin lock during napi_complete_done Oscar Maes
2026-05-25 13:53   ` Andrew Lunn
2026-05-25 15:46   ` Jakub Kicinski
2026-05-25 12:54 ` [PATCH net-next v2 2/2] pcnet32: switch to napi_alloc_skb() and napi_gro_receive() Oscar Maes
2026-05-25 15:45   ` Jakub Kicinski
2026-05-28 14:28     ` Oscar Maes
2026-05-28 15:07       ` Jakub Kicinski
2026-05-28 17:05         ` Oscar Maes
2026-05-28 19:12           ` Jakub Kicinski
2026-05-31 16:51             ` Oscar Maes
2026-05-31 20:09               ` Andrew Lunn
2026-06-02 16:37                 ` 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=20260525125437.4061-1-oscmaes92@gmail.com \
    --to=oscmaes92@gmail$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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