From: Stephen Hemminger <stephen@networkplumber.org>
To: Michael Richardson via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] WSL2 + fq_codel
Date: Sat, 25 Feb 2023 12:54:25 -0800 [thread overview]
Message-ID: <20230225125425.7d440ba9@hermes.local> (raw)
In-Reply-To: <27972.1677357422@localhost>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
On Sat, 25 Feb 2023 15:37:02 -0500
Michael Richardson via Bloat <bloat@lists.bufferbloat.net> wrote:
> Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
> > I so want to believe... I so want to believe... can anyone confirm?
>
> > https://raw.githubusercontent.com/microsoft/WSL2-Linux-Kernel/linux-msft-wsl-5.15.y/Microsoft/config-wsl
>
> But, AFAIK, WSL isn't a kernel. It's an implementation of the Linux ABI on
> top of Windows service(s). If you told me that they build some of it from
> actual Linux kernel sources, I'd believe you. (Rather like User-Mode-Linux)
>
> If you told me that they have a kernel that they build for when they actually
> spin up an actual VM (such as to run containers) that would also be unsurprising.
>
> > ...
>
> > CONFIG_NET_SCH_DEFAULT=y
> > CONFIG_DEFAULT_FQ_CODEL=y
> > # CONFIG_DEFAULT_PFIFO_FAST is not set
> > CONFIG_DEFAULT_NET_SCH="fq_codel"
>
> It would be nice if the billion windows desktops started doing
> something better, but I don't think it will help observed latency.
> The real question is what the default schedule for the default Azure Linux VM
> is.
>
I think WSL2 is actually a full Linux VM running in Hyper-V.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-25 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 18:54 Dave Taht
2023-02-25 20:37 ` Michael Richardson
2023-02-25 20:54 ` Stephen Hemminger [this message]
2023-02-25 22:07 ` Dave Taht
2023-02-27 12:10 ` Maximilian Bachl
2023-02-27 23:32 ` Stephen Hemminger
2023-02-27 23:36 ` Dave Taht
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=20230225125425.7d440ba9@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
/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