netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Paul Barker <paul.barker.ct@bp.renesas.com>
Cc: s.shtylyov@omp.ru, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com,
	niklas.soderlund+renesas@ragnatech.se, horms@kernel.org,
	biju.das.jz@bp.renesas.com, claudiu.beznea.uj@bp.renesas.com,
	yoshihiro.shimoda.uh@renesas.com, netdev@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH v5 0/7] Improve GbEth performance on Renesas RZ/G2L and related SoCs
Date: Thu, 06 Jun 2024 08:20:31 +0000	[thread overview]
Message-ID: <171766203185.3557.7483807066243458681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240604072825.7490-1-paul.barker.ct@bp.renesas.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue,  4 Jun 2024 08:28:18 +0100 you wrote:
> This series aims to improve performance of the GbEth IP in the Renesas
> RZ/G2L SoC family and the RZ/G3S SoC, which use the ravb driver. Along
> the way, we do some refactoring and ensure that napi_complete_done() is
> used in accordance with the NAPI documentation for both GbEth and R-Car
> code paths.
> 
> Much of the performance improvement comes from enabling SW IRQ
> Coalescing for all SoCs using the GbEth IP, and NAPI Threaded mode for
> single core SoCs using the GbEth IP. These can be enabled/disabled at
> runtime via sysfs, but our goal is to set sensible defaults which get
> good performance on the affected SoCs.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/7] net: ravb: Simplify poll & receive functions
    https://git.kernel.org/netdev/net-next/c/118e640af30c
  - [net-next,v5,2/7] net: ravb: Align poll function with NAPI docs
    https://git.kernel.org/netdev/net-next/c/b0e0e20dc60e
  - [net-next,v5,3/7] net: ravb: Refactor RX ring refill
    https://git.kernel.org/netdev/net-next/c/37a01c12e9e8
  - [net-next,v5,4/7] net: ravb: Refactor GbEth RX code path
    https://git.kernel.org/netdev/net-next/c/3ee43f09cb2c
  - [net-next,v5,5/7] net: ravb: Enable SW IRQ Coalescing for GbEth
    https://git.kernel.org/netdev/net-next/c/7b39c1814ce3
  - [net-next,v5,6/7] net: ravb: Use NAPI threaded mode on 1-core CPUs with GbEth IP
    https://git.kernel.org/netdev/net-next/c/65c482bc226a
  - [net-next,v5,7/7] net: ravb: Allocate RX buffers via page pool
    https://git.kernel.org/netdev/net-next/c/966726324b7b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-06  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  7:28 [net-next PATCH v5 0/7] Improve GbEth performance on Renesas RZ/G2L and related SoCs Paul Barker
2024-06-04  7:28 ` [net-next PATCH v5 1/7] net: ravb: Simplify poll & receive functions Paul Barker
2024-06-04  7:28 ` [net-next PATCH v5 2/7] net: ravb: Align poll function with NAPI docs Paul Barker
2024-06-04 20:47   ` Sergey Shtylyov
2024-06-04  7:28 ` [net-next PATCH v5 3/7] net: ravb: Refactor RX ring refill Paul Barker
2024-06-04  7:28 ` [net-next PATCH v5 4/7] net: ravb: Refactor GbEth RX code path Paul Barker
2024-06-05 18:51   ` Sergey Shtylyov
2024-06-04  7:28 ` [net-next PATCH v5 5/7] net: ravb: Enable SW IRQ Coalescing for GbEth Paul Barker
2024-06-04  7:28 ` [net-next PATCH v5 6/7] net: ravb: Use NAPI threaded mode on 1-core CPUs with GbEth IP Paul Barker
2024-06-04  7:28 ` [net-next PATCH v5 7/7] net: ravb: Allocate RX buffers via page pool Paul Barker
2024-06-05 20:14   ` Sergey Shtylyov
2024-06-06  8:20 ` 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=171766203185.3557.7483807066243458681.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=pabeni@redhat.com \
    --cc=paul.barker.ct@bp.renesas.com \
    --cc=s.shtylyov@omp.ru \
    --cc=yoshihiro.shimoda.uh@renesas.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).