From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht via Bloat <bloat@lists.bufferbloat.net>
Cc: Dave Taht <dave.taht@gmail.com>,
Michael Welzl <michawe@ifi.uio.no>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [Bloat] Trying to *really* understand Linux pacing
Date: Wed, 7 Feb 2024 07:03:01 -0800 [thread overview]
Message-ID: <20240207070301.30c92e23@hermes.local> (raw)
In-Reply-To: <CAA93jw6di-ypNHH0kz70mhYitT_wsbpZR4gMbSx7FEpSvHx3qg@mail.gmail.com>
On Wed, 7 Feb 2024 07:05:27 -0500
Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
> I also tend to think that attempting it in various cloudy
> environments and virtualization schemes, and with certain drivers, the
> side effects are not as well understood as I would like. For example,
> AWS's nitro lacks BQL as does virtio-net.
FYI - Microsoft Azure drivers don't do BQL either.
Both netvsc and mana.
The problem is that implementing BQL is not as easy as it looks
and has possibility of introducing bugs. One big customer with a stuck
connection totally negates any benefit!
For virtio, there have been several attempts at BQL and they never worked
perfectly.
prev parent reply other threads:[~2024-02-07 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 11:56 Michael Welzl
2024-02-07 12:05 ` Dave Taht
2024-02-07 12:08 ` Michael Welzl
2024-02-07 12:20 ` Dave Taht
2024-02-07 20:13 ` Neal Cardwell
2024-02-19 13:54 ` Michael Welzl
2024-02-19 14:02 ` Dave Taht
2024-02-07 15:03 ` Stephen Hemminger [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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240207070301.30c92e23@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=michawe@ifi.uio.no \
--cc=netdev@vger.kernel.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