From: Brett Sheffield <bacs@librecast.net>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Simon Schippers <simon.schippers@tu-dortmund.de>,
regressions@lists.linux.dev, netdev@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
Tim Gebauer <tim.gebauer@tu-dortmund.de>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowang@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] tun/tap & vhost-net: multi-threaded network performance
Date: Fri, 3 Jul 2026 16:13:49 +0200 [thread overview]
Message-ID: <akfDnfkgorxJ_Q6G@karahi.librecast.net> (raw)
In-Reply-To: <20260702185420-mutt-send-email-mst@kernel.org>
On 2026-07-02 18:55, Michael S. Tsirkin wrote:
> On Thu, Jul 02, 2026 at 01:07:47PM +0200, Brett Sheffield wrote:
> > On 2026-07-02 09:24, Simon Schippers wrote:
> > > On 7/1/26 22:56, Michael S. Tsirkin wrote:
> > > > - does it help to increase the tun queue size?
> > >
> > > I agree, this would be great to know.
I tried adding a queue (qdisc pfifo limit 500) on both host and guest - no
apparent difference in drops or performance.
If there's any other setting you want me to try, let me know.
> Maybe it's the supposedly rare case? Does this change anything
> for you?
I also tried both patches, but again, no noticable difference.
--
Brett Sheffield (he/him)
Librecast - Decentralising the Internet with Multicast
https://librecast.net/
https://blog.brettsheffield.com/
next prev parent reply other threads:[~2026-07-03 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 19:16 [REGRESSION][BISECTED] tun/tap & vhost-net: multi-threaded network performance Brett Sheffield
2026-07-01 20:56 ` Michael S. Tsirkin
2026-07-02 7:24 ` Simon Schippers
2026-07-02 7:42 ` Michael S. Tsirkin
2026-07-02 8:01 ` Simon Schippers
2026-07-02 11:07 ` Brett Sheffield
2026-07-02 22:44 ` Michael S. Tsirkin
2026-07-03 10:34 ` Simon Schippers
2026-07-02 22:55 ` Michael S. Tsirkin
2026-07-03 10:35 ` Simon Schippers
2026-07-03 14:13 ` Brett Sheffield [this message]
2026-07-03 14:19 ` Michael S. Tsirkin
2026-07-03 10:41 ` Simon Schippers
2026-07-03 11:55 ` Michael S. Tsirkin
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=akfDnfkgorxJ_Q6G@karahi.librecast.net \
--to=bacs@librecast.net \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=simon.schippers@tu-dortmund.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox