Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Luca Muscariello <luca.muscariello@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Modification of DRR with deficit saving
Date: Thu, 4 Jan 2018 16:23:07 +0100	[thread overview]
Message-ID: <CAHx=1M6=HDOgfO45uBNySmRfKqhdkSs-Jj_Jwa9KBg9jm8DpOQ@mail.gmail.com> (raw)
In-Reply-To: <F4EFD094-79B4-4C4B-95E7-CB7FFA3755A5@gmail.com>

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

I think the closest scheduler to Cake is this one, if I have to compare:

https://team.inria.fr/rap/files/2013/12/KOR05.pdf

J. Roberts et al. Implicit Service Differentiation using Deficit Round
Robin, In Proc of ITC 2005.

Luca


On Thu, Jan 4, 2018 at 4:01 PM, Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 4 Jan, 2018, at 4:29 pm, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> >
> > This popped up in my Google Scholar notifications:
> >
> > https://atlas.informatik.uni-tuebingen.de/~menth/papers/Menth18b.pdf
> >
> > Basically, they are proposing to permit a queue to accumulate a larger
> > deficit while empty to allow light users to achieve the same throughput
> > as heavy users (users being an endpoint with potentially multiple
> > flows).
> >
> > Not sure how useful this really is, but it's somewhat related to Cake's
> > src/dst user fairness feature, so may be of interest.
>
> They're trying to solve the same problem as DRR++ does, not the same one
> as Triple Isolation does.
>
> As a result, they've basically proposed a bugfix to the original DRR (ie.
> you should keep replenishing the deficit until it saturates, even if the
> queue is temporarily empty), without gaining the full benefit of DRR++.
>
> Not interesting at all.
>
>  - Jonathan Morton
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>

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

  reply	other threads:[~2018-01-04 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 14:29 Toke Høiland-Jørgensen
2018-01-04 14:52 ` Dave Taht
2018-01-04 15:01 ` Jonathan Morton
2018-01-04 15:23   ` Luca Muscariello [this message]
2018-01-04 15:42     ` Dave Taht
2018-01-04 15:53       ` Luca Muscariello
2018-01-04 16:20         ` Dave Taht
2018-01-04 16:24           ` Luca Muscariello
2018-01-04 16:39             ` Dave Taht
2018-01-05  8:19           ` Pete Heist
2018-01-04 15:56       ` Sebastian Moeller

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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAHx=1M6=HDOgfO45uBNySmRfKqhdkSs-Jj_Jwa9KBg9jm8DpOQ@mail.gmail.com' \
    --to=luca.muscariello@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=toke@toke.dk \
    /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