From: Jakub Kicinski <kuba@kernel.org>
To: Neal Cardwell <ncardwell@google.com>
Cc: Teodor Milkov <zimage@icdsoft.com>,
netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com
Subject: Re: Download throttling with kernel 6.6 (in KVM guests)
Date: Mon, 6 Jan 2025 19:19:16 -0800 [thread overview]
Message-ID: <20250106191916.6e26b3fd@kernel.org> (raw)
In-Reply-To: <CADVnQynBPVr0qX2pu7FNwk6Y1BaW-pGf=JReJPCAj9RP=6t9_w@mail.gmail.com>
On Mon, 6 Jan 2025 21:50:02 -0500 Neal Cardwell wrote:
> On Mon, Jan 6, 2025 at 4:20 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > On Mon, 6 Jan 2025 22:15:37 +0200 Teodor Milkov wrote:
> > > Hello,
> > >
> > > Following up on my previous email, I’ve found the issue occurs
> > > specifically with the |virtio-net| driver in KVM guests. Switching to
> > > the |e1000| driver resolves the slowdown entirely, with no throttling in
> > > subsequent downloads.
> > >
> > > The reproducer and observations remain the same, but this detail might
> > > help narrow down the issue.
> >
> > Let's CC the virtio maintainers, then.
> >
> > The fact that a 300ms sleep between connections makes the problem
> > go away is a bit odd from the networking perspective.
> >
> > You may need to find a way to automate the test and try to bisect
> > it down :( This may help: https://github.com/arighi/virtme-ng
>
> IIUC, from Teodor's earlier message in the thread it sounds like he
> was able to bisect the issue; he mentioned that git bisect traced the
> regression to the commit:
>
> dfa2f0483360 ("tcp: get rid of sysctl_tcp_adv_win_scale")
My bad. I think I looked at it last week and couldn't figure out
why the sleep make any difference.
prev parent reply other threads:[~2025-01-07 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 12:31 Download throttling with kernel 6.6 (in KVM guests) Teodor Milkov
2025-01-06 20:15 ` Teodor Milkov
2025-01-06 21:15 ` Neal Cardwell
2025-01-06 21:20 ` Jakub Kicinski
2025-01-07 2:50 ` Neal Cardwell
2025-01-07 3:19 ` Jakub Kicinski [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=20250106191916.6e26b3fd@kernel.org \
--to=kuba@kernel.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=zimage@icdsoft.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;
as well as URLs for NNTP newsgroup(s).