All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, tariqt@nvidia.com, idosch@idosch.org,
	hawk@kernel.org, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org
Subject: Re: [PATCH net-next v3 0/4] eth: mlx4: use the page pool for Rx buffers
Date: Tue, 18 Feb 2025 23:40:32 +0000	[thread overview]
Message-ID: <173992203251.66396.7782136856830583801.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250213010635.1354034-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 12 Feb 2025 17:06:31 -0800 you wrote:
> Convert mlx4 to page pool. I've been sitting on these patches for
> over a year, and Jonathan Lemon had a similar series years before.
> We never deployed it or sent upstream because it didn't really show
> much perf win under normal load (admittedly I think the real testing
> was done before Ilias's work on recycling).
> 
> During the v6.9 kernel rollout Meta's CDN team noticed that machines
> with CX3 Pro (mlx4) are prone to overloads (double digit % of CPU time
> spent mapping buffers in the IOMMU). The problem does not occur with
> modern NICs, so I dusted off this series and reportedly it still works.
> And it makes the problem go away, no overloads, perf back in line with
> older kernels. Something must have changed in IOMMU code, I guess.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/4] eth: mlx4: create a page pool for Rx
    (no matching commit)
  - [net-next,v3,2/4] eth: mlx4: don't try to complete XDP frames in netpoll
    https://git.kernel.org/netdev/net-next/c/8fdeafd66eda
  - [net-next,v3,3/4] eth: mlx4: remove the local XDP fast-recycling ring
    (no matching commit)
  - [net-next,v3,4/4] eth: mlx4: use the page pool for Rx buffers
    (no matching commit)

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



      parent reply	other threads:[~2025-02-18 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13  1:06 [PATCH net-next v3 0/4] eth: mlx4: use the page pool for Rx buffers Jakub Kicinski
2025-02-13  1:06 ` [PATCH net-next v3 1/4] eth: mlx4: create a page pool for Rx Jakub Kicinski
2025-02-18 12:10   ` Tariq Toukan
2025-02-13  1:06 ` [PATCH net-next v3 2/4] eth: mlx4: don't try to complete XDP frames in netpoll Jakub Kicinski
2025-02-18 12:11   ` Tariq Toukan
2025-02-13  1:06 ` [PATCH net-next v3 3/4] eth: mlx4: remove the local XDP fast-recycling ring Jakub Kicinski
2025-02-18 12:12   ` Tariq Toukan
2025-02-13  1:06 ` [PATCH net-next v3 4/4] eth: mlx4: use the page pool for Rx buffers Jakub Kicinski
2025-02-18 12:13   ` Tariq Toukan
2025-02-18 23: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=173992203251.66396.7782136856830583801.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@idosch.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tariqt@nvidia.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.