From: patchwork-bot+netdevbpf@kernel.org
To: Simon Schippers <simon.schippers@tu-dortmund.de>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
jasowangio@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
mst@redhat.com, eperezma@redhat.com, horms@kernel.org,
tim.gebauer@tu-dortmund.de, brett@librecast.net,
kvm@vger.kernel.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/4] Revert "tun/tap & vhost-net: apply qdisc backpressure on full ptr_ring to reduce TX drops"
Date: Thu, 30 Jul 2026 00:20:11 +0000 [thread overview]
Message-ID: <178537081189.3294584.1292356149475658515.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260728092240.250257-1-simon.schippers@tu-dortmund.de>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Jul 2026 11:22:36 +0200 you wrote:
> Commit 1d6e569b7d0c ("tun/tap & vhost-net: avoid ptr_ring tail-drop when
> a qdisc is present") did not show a relevant performance regression in my
> testing, but on Brett Sheffield's librecast testbed it causes a
> significant throughput drop in an IPv6 multicast testcase. The regression
> can be pinpointed to multiple iperf3 TCP threads sending: for 8 threads
> the throughput dropped from 13.5 Gbit/s to 9.13 Gbit/s.
>
> [...]
Here is the summary with links:
- [net,1/4] Revert "tun/tap & vhost-net: avoid ptr_ring tail-drop when a qdisc is present"
https://git.kernel.org/netdev/net/c/f11b48aa674b
- [net,2/4] Revert "ptr_ring: move free-space check into separate helper"
https://git.kernel.org/netdev/net/c/6bc85579c3bb
- [net,3/4] Revert "vhost-net: wake queue of tun/tap after ptr_ring consume"
https://git.kernel.org/netdev/net/c/8f83be72d9f5
- [net,4/4] Revert "tun/tap: add ptr_ring consume helper with netdev queue wakeup"
https://git.kernel.org/netdev/net/c/c3da92af07ea
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-30 0:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 9:22 [PATCH net 0/4] Revert "tun/tap & vhost-net: apply qdisc backpressure on full ptr_ring to reduce TX drops" Simon Schippers
2026-07-28 9:22 ` [PATCH net 1/4] Revert "tun/tap & vhost-net: avoid ptr_ring tail-drop when a qdisc is present" Simon Schippers
2026-07-28 9:22 ` [PATCH net 2/4] Revert "ptr_ring: move free-space check into separate helper" Simon Schippers
2026-07-28 9:22 ` [PATCH net 3/4] Revert "vhost-net: wake queue of tun/tap after ptr_ring consume" Simon Schippers
2026-07-28 9:22 ` [PATCH net 4/4] Revert "tun/tap: add ptr_ring consume helper with netdev queue wakeup" Simon Schippers
2026-07-28 19:22 ` [PATCH net 0/4] Revert "tun/tap & vhost-net: apply qdisc backpressure on full ptr_ring to reduce TX drops" Michael S. Tsirkin
2026-07-30 0: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=178537081189.3294584.1292356149475658515.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brett@librecast.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.schippers@tu-dortmund.de \
--cc=tim.gebauer@tu-dortmund.de \
--cc=virtualization@lists.linux.dev \
--cc=willemdebruijn.kernel@gmail.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