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, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	alexanderduyck@fb.com
Subject: Re: [PATCH net] eth: fbnic: ring the doorbell if a burst ends in a drop
Date: Thu, 17 Sep 2026 00:40:10 +0000	[thread overview]
Message-ID: <178960561037.3354472.15026253707073838985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915022327.913218-1-kuba@kernel.org>

Hello:

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

On Mon, 14 Sep 2026 19:23:27 -0700 you wrote:
> fbnic_tx_map() skips the doorbell write, and the completion request,
> for every packet handed to it with xmit_more set, counting on the
> packet which ends the burst to publish them all. When that packet is
> dropped instead - skb_put_padto(), skb_cow_head() or a DMA mapping
> failure - nothing rings. The descriptors of the preceding packets stay
> invisible to the HW until the next transmit on that queue, which for a
> burst-then-idle workload may never come.
> 
> [...]

Here is the summary with links:
  - [net] eth: fbnic: ring the doorbell if a burst ends in a drop
    https://git.kernel.org/netdev/net/c/490599ab2313

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-09-17  0:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  2:23 [PATCH net] eth: fbnic: ring the doorbell if a burst ends in a drop Jakub Kicinski
2026-09-16 12:35 ` Simon Horman
2026-09-17  0: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=178960561037.3354472.15026253707073838985.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexanderduyck@fb.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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 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.