Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
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>
Subject: Re: [Cerowrt-devel] [Bloat] capacity awareness for the deadline scheduler
Date: Mon, 01 Jun 2020 11:58:37 -0400	[thread overview]
Message-ID: <18883.1591027117@localhost> (raw)
In-Reply-To: <CAA93jw64=GZUs2XJbjfCYAHTKnMETDXQcu1zFLfJSfA8CWWVGw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]


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    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-06-01 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 21:39 [Cerowrt-devel] " Dave Taht
2020-06-01 15:58 ` Michael Richardson [this message]
2020-06-01 20:35   ` [Cerowrt-devel] [Bloat] " Dave Taht
2020-06-01 16:02 ` Michael Richardson
2020-06-01 20:31   ` 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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18883.1591027117@localhost \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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