From: Jonathan Morton <chromatix99@gmail.com>
To: Luca Muscariello <luca.muscariello@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
Cake List <cake@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Make-wifi-fast] Van Jacobson's slides on timing wheels at netdevconf
Date: Sat, 21 Jul 2018 17:38:22 +0300 [thread overview]
Message-ID: <1A06B0BB-4B2F-4E94-B947-EF41BCC3F18C@gmail.com> (raw)
In-Reply-To: <CAHx=1M707THPD1FoD+V=9BdVBKYVbzDX09t7yrdoA4hGVcXH6g@mail.gmail.com>
> On 20 Jul, 2018, at 5:47 pm, Luca Muscariello <luca.muscariello@gmail.com> wrote:
>
> and C) you can implement any packet scheduler using a timing wheel using virtual times.
To do this perfectly, you have to assume that no packets will arrive within your scheduling horizon which should be scheduled within that horizon.
An example of such a situation would be sparse flows in DRR++, which is a key part of fq_codel and Cake. So to implement DRR++ using timing wheels, you have to choose your scheduling horizon carefully so as to minimise the delay to sparse packets.
Given that task scheduling latency in Linux is on the order of 1ms, a horizon of this magnitude could be acceptable. But dedicated hardware could do better still.
- Jonathan Morton
next prev parent reply other threads:[~2018-07-21 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 14:09 [Bloat] " Dave Taht
2018-07-20 14:47 ` [Bloat] [Make-wifi-fast] " Luca Muscariello
2018-07-21 14:38 ` Jonathan Morton [this message]
2018-07-23 12:52 ` Mikael Abrahamsson
2018-07-23 15:36 ` Dave Taht
2018-07-23 17:26 ` dpreed
2018-07-21 13:19 ` [Bloat] " Matthias Tafelmeier
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=1A06B0BB-4B2F-4E94-B947-EF41BCC3F18C@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=luca.muscariello@gmail.com \
--cc=make-wifi-fast@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