mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Zahka <daniel.zahka@gmail.com>
Cc: alexanderduyck@fb.com, kuba@kernel.org, kernel-team@meta.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] mpnic: add NAPI buffer depletion check
Date: Tue, 06 Oct 2026 00:00:11 +0000	[thread overview]
Message-ID: <179124481127.1944959.8347251870920049809.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001-linux-mpnic-v1-0-6422ee74233a@gmail.com>

Hello:

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

On Thu, 01 Oct 2026 09:38:57 -0700 you wrote:
> This series provides a buffer depletion check to unwedge Rx processing
> when page pool allocations have failed. Patch 4 has a more detailed
> description of the events that lead to the wedge, but the high level
> idea is that when page pool allocations fail, the buffer descriptor ring
> can run low, and when that happens the device will drop Rx packets and
> not raise interrupts, which causes the NAPI event loop not to be
> scheduled, so new buffers are not posted.
> 
> [...]

Here is the summary with links:
  - [net-next,1/4] eth: mpnic: use WRITE_ONCE() for BDQ head and tail updates
    https://git.kernel.org/netdev/net-next/c/0de04d82b63c
  - [net-next,2/4] eth: mpnic: add a service task
    https://git.kernel.org/netdev/net-next/c/d990f86c796b
  - [net-next,3/4] eth: mpnic: set Rx buffer minimums using page size and mtu
    https://git.kernel.org/netdev/net-next/c/9e072eda51ca
  - [net-next,4/4] eth: mpnic: add a NAPI depletion check
    https://git.kernel.org/netdev/net-next/c/56f2178ff7f6

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



      parent reply	other threads:[~2026-10-06  0:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 16:38 Daniel Zahka
2026-10-01 16:38 ` [PATCH net-next 1/4] eth: mpnic: use WRITE_ONCE() for BDQ head and tail updates Daniel Zahka
2026-10-01 16:38 ` [PATCH net-next 2/4] eth: mpnic: add a service task Daniel Zahka
2026-10-01 16:39 ` [PATCH net-next 3/4] eth: mpnic: set Rx buffer minimums using page size and mtu Daniel Zahka
2026-10-03  0:50   ` Harshitha Ramamurthy
2026-10-05 11:15     ` Daniel Zahka
2026-10-01 16:39 ` [PATCH net-next 4/4] eth: mpnic: add a NAPI depletion check Daniel Zahka
2026-10-03  0:53   ` Harshitha Ramamurthy
2026-10-05 11:42     ` Daniel Zahka
2026-10-01 16:45 ` [PATCH net-next 0/4] mpnic: add NAPI buffer " netdev-bot+sinfo
2026-10-01 18:26   ` Daniel Zahka
2026-10-03  0:54 ` Harshitha Ramamurthy
2026-10-06  0:00 ` 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=179124481127.1944959.8347251870920049809.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexanderduyck@fb.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=daniel.zahka@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®