General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] pquic + fq_codel + lowrtt + multipath
Date: Sun, 20 Dec 2020 12:13:58 -0800	[thread overview]
Message-ID: <CALQXh-OeFz3uJsqtfpW75kODRLqoDSj-NnMtTj_A1dBStZzyUg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4NFa1+9nXaLYUjtwqhqjaVpyTjVbgYEBRV5aTivFONvg@mail.gmail.com>

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

Those are great results.

I've been thinking for a while that algorithms / techniques like fq-codel
would be great if packaged into library form where they could be utilized
by application-layers.  Obviously, not all application-layer queues can
deal with loss like TCP, but for all those that can, it would be a really
nice thing to have.

And for those loads that cannot, maybe they should be rethought into ways
to add better backpressure...

On Sun, Dec 20, 2020 at 10:54 AM Dave Taht <dave.taht@gmail.com> wrote:

> the lowrtt scheduler is pretty impressive as an example of what can be
> additionally achieved at the application layer. See pp 49-
>
> https://www.diva-portal.org/smash/get/diva2:1451478/FULLTEXT02
>
> --
> "For a successful technology, reality must take precedence over public
> relations, for Mother Nature cannot be fooled" - Richard Feynman
>
> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 1840 bytes --]

      reply	other threads:[~2020-12-20 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 18:54 Dave Taht
2020-12-20 20:13 ` Aaron Wood [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=CALQXh-OeFz3uJsqtfpW75kODRLqoDSj-NnMtTj_A1dBStZzyUg@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=bloat@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