From: "Michael S. Tsirkin" <mst@redhat.com>
To: Simon Schippers <simon.schippers@tu-dortmund.de>
Cc: Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowangio@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Tim Gebauer <tim.gebauer@tu-dortmund.de>,
Brett Sheffield <brett@librecast.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] tun/tap & vhost-net: make qdisc backpressure opt-in via IFF_BACKPRESSURE
Date: Wed, 22 Jul 2026 04:09:25 -0400 [thread overview]
Message-ID: <20260722040722-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <8814700c-7549-4d12-b657-c990dfeec14f@tu-dortmund.de>
On Wed, Jul 22, 2026 at 08:39:38AM +0200, Simon Schippers wrote:
> On 7/22/26 08:07, Michael S. Tsirkin wrote:
> > On Tue, Jul 21, 2026 at 10:07:15AM -0700, Jakub Kicinski wrote:
> >> On Tue, 21 Jul 2026 10:59:52 -0400 Michael S. Tsirkin wrote:
> >>>>> I prefer applying it, but you maintainers must decide that.
> >>>>
> >>>> Hi,
> >>>> just a gentle ping.
> >>>> Has there been any decision on this patch?
> >>>
> >>> Hi netdev maintainers. Given there's a perf regression otherwise,
> >>> we should either take this or revert the original and reapply
> >>> in next.
> >>
> >> Revert, please. We were AFK and are now working thru a backlog
> >> of 1k patches. The new IFF_* flag needs scrutiny we can't afford
> >> at present.
> >
> > okay. Simon can you post it pls or should I? And once merged post
> > re-apply for next with the flag included?
> >
> > Thanks!
> >
>
> Would be great if you could do the revert.
> I don't want to mess it up. :P
>
> For the re-apply:
> I can post a v13 to net-next soon with the flag included
> into the existing commits.
> Or would you rather take v12 plus this opt-in commit as-is?
>
> Thanks!
jacub if the revert goes into next what is the process to
target a patch on top of it for net-next? Thanks!
next prev parent reply other threads:[~2026-07-22 8:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 9:55 [PATCH net v3] tun/tap & vhost-net: make qdisc backpressure opt-in via IFF_BACKPRESSURE Simon Schippers
2026-07-09 16:06 ` Brett Sheffield
2026-07-14 6:57 ` Simon Schippers
2026-07-14 13:40 ` Michael S. Tsirkin
2026-07-14 16:50 ` Simon Schippers
2026-07-21 14:04 ` Simon Schippers
2026-07-21 14:59 ` Michael S. Tsirkin
2026-07-21 17:07 ` Jakub Kicinski
2026-07-22 6:07 ` Michael S. Tsirkin
2026-07-22 6:39 ` Simon Schippers
2026-07-22 8:09 ` Michael S. Tsirkin [this message]
2026-07-15 14:01 ` [LTP] " kernel test robot
2026-07-15 14:01 ` kernel test robot
2026-07-15 14:32 ` Simon Schippers
2026-07-15 14:32 ` [LTP] " Simon Schippers
2026-07-16 1:22 ` Oliver Sang
2026-07-16 1:22 ` [LTP] " Oliver Sang
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=20260722040722-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett@librecast.net \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.schippers@tu-dortmund.de \
--cc=skhan@linuxfoundation.org \
--cc=tim.gebauer@tu-dortmund.de \
--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 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.