From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mcr@sandelman.ca>
Received: from tuna.sandelman.ca (desktop4.sandelman.ca [209.87.249.16])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 535A73B2A4;
 Mon,  1 Jun 2020 11:58:42 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
 by tuna.sandelman.ca (Postfix) with ESMTP id 1011638A0E;
 Mon,  1 Jun 2020 11:56:17 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1])
 by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id LLW01GsB8E2s; Mon,  1 Jun 2020 11:56:16 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247])
 by tuna.sandelman.ca (Postfix) with ESMTP id DE3A238A0D;
 Mon,  1 Jun 2020 11:56:15 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1])
 by sandelman.ca (Postfix) with ESMTP id 37AA4478;
 Mon,  1 Jun 2020 11:58:37 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>,
 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
In-Reply-To: <CAA93jw64=GZUs2XJbjfCYAHTKnMETDXQcu1zFLfJSfA8CWWVGw@mail.gmail.com>
References: <CAA93jw64=GZUs2XJbjfCYAHTKnMETDXQcu1zFLfJSfA8CWWVGw@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;
 <'$9xN5Ub#
 z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
 micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Mon, 01 Jun 2020 11:58:37 -0400
Message-ID: <18883.1591027117@localhost>
Subject: Re: [Cerowrt-devel] [Bloat] capacity awareness for the deadline
	scheduler
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
 <cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2020 15:58:42 -0000

--=-=-=
Content-Type: text/plain


Dave Taht <dave.taht@gmail.com> wrote:
    > Gradually, people seem to be getting more and more about basic queue theory.
    > https://lwn.net/SubscriberLink/821578/ef5d913a20977921/

Having skimmed the article, which seems to be mostly about CPU scheduling, I
have a question.

Does the availability of better *CPU* scheduling make it easier to do better
TCP pacing?  Maybe that was your entire point?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl7VJawACgkQgItw+93Q
3WXpmggAmsqgrBiUFsuAJZEqIKYuD91yUGxuSqp8d1na71zIubUnChgSYKDdfb1v
iMaMfF4eNfjXMvXKad6hPdIc8SIczqTeVe9Eg03YEntN4Cn5Ft8Sp2x01NRVcknx
sI2Ew1u1fVDd7pbx0qX+heCllYXSj3uCKUpSliJO5PUkh3AvZm3jTTqKoXC5QxA0
xWD1aJO7tcvtHLYYw1Rku7RaXh0oG+i0j0fpQfk2I5RN6Cov2eCekuSOMSxiDQZL
MIFqlU9jLfIxLYgguhasksXU1ruxkXO6ezBQJ7w4L2Z5rOLdJ+DPcEn/TeeFmjol
Y+w8tuzaZhDxsYUa41tC9F5222/0eg==
=+yJz
-----END PGP SIGNATURE-----
--=-=-=--