mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Torsten Krah <krah.tm@gmail.com>
To: virtualization@lists.linux-foundation.org
Cc: Markus Fohrer <markus.fohrer@webked.de>,
	mst@redhat.com,  jasowang@redhat.com, davem@davemloft.net,
	edumazet@google.com,  netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] Massive virtio-net throughput drop in guest VM with Linux 6.8+
Date: Fri, 04 Apr 2025 09:59:19 +0200	[thread overview]
Message-ID: <4d0c0cb9e9d513bf9ba81346ea72c9e58359ff93.camel@gmail.com> (raw)
In-Reply-To: <1d388413ab9cfd765cd2c5e05b5e69cdb2ec5a10.camel@webked.de>

Am Mittwoch, dem 02.04.2025 um 23:12 +0200 schrieb Markus Fohrer:
> When running on a host system equipped with a Broadcom NetXtreme-E
> (bnxt_en) NIC and AMD EPYC CPUs, the network throughput in the guest
> drops to 100–200 KB/s. The same guest configuration performs normally
> (~100 MB/s) when using kernel 6.8.0 or when the VM is moved to a host
> with Intel NICs.

Hi,

as I am affected too, here is the link to the Ubuntu issue, just in
case someone wants to have a look:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098961

We're seeing lots of those in dmesg output:

[  561.505323] net_ratelimit: 1396 callbacks suppressed
[  561.505339] ens18: bad gso: type: 4, size: 1448
[  561.505343] ens18: bad gso: type: 4, size: 1448
[  561.507270] ens18: bad gso: type: 4, size: 1448
[  561.508257] ens18: bad gso: type: 4, size: 1448
[  561.511432] ens18: bad gso: type: 4, size: 1448
[  561.511452] ens18: bad gso: type: 4, size: 1448
[  561.514719] ens18: bad gso: type: 4, size: 1448
[  561.514966] ens18: bad gso: type: 4, size: 1448
[  561.518553] ens18: bad gso: type: 4, size: 1448
[  561.518781] ens18: bad gso: type: 4, size: 1448
[  566.506044] net_ratelimit: 1363 callbacks suppressed


And another interesting thing we observed - at least in our environment
- that we can trigger that regression only with IPv4 traffic (bad
performance and lots of bad gso messages) - if we only use IPv6, it
does work (good performance and not one bad gso message).

kind regards

Torsten


  parent reply	other threads:[~2025-04-04  7:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02 21:12 Markus Fohrer
2025-04-03 13:04 ` Michael S. Tsirkin
2025-04-03 13:51   ` Markus Fohrer
2025-04-03 14:03     ` Michael S. Tsirkin
2025-04-03 14:26       ` Willem de Bruijn
2025-04-03 20:00         ` Markus Fohrer
2025-04-03 20:35         ` Markus Fohrer
2025-04-03 20:07       ` Markus Fohrer
2025-04-03 21:06         ` Michael S. Tsirkin
2025-04-03 21:24           ` Markus Fohrer
2025-04-03 21:49             ` Willem de Bruijn
2025-04-03 22:05             ` Michael S. Tsirkin
2025-04-04 11:32               ` Markus Fohrer
2025-04-04  8:16   ` Markus Fohrer
2025-04-04  8:29     ` Michael S. Tsirkin
2025-04-04  8:52       ` Markus Fohrer
2025-04-04 11:40         ` Markus Fohrer
2025-04-04 15:13           ` Willem de Bruijn
2025-04-04 20:23             ` Markus Fohrer
2025-04-04 22:05             ` Ilya Maximets
2025-04-05  6:15               ` Markus Fohrer
2025-04-05 12:18                 ` Ilya Maximets
2025-04-04  7:59 ` Torsten Krah [this message]
2025-04-04  8:26   ` 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=4d0c0cb9e9d513bf9ba81346ea72c9e58359ff93.camel@gmail.com \
    --to=krah.tm@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.fohrer@webked.de \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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®