From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Luca Muscariello <luca.muscariello@gmail.com>,
Cake List <cake@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Bloat] Van Jacobson's slides on timing wheels at netdevconf
Date: Mon, 23 Jul 2018 14:52:24 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1807231444540.14354@uplift.swm.pp.se> (raw)
In-Reply-To: <1A06B0BB-4B2F-4E94-B947-EF41BCC3F18C@gmail.com>
On Sat, 21 Jul 2018, Jonathan Morton wrote:
> 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.
At the spring IETF, there was talk from IEEE person about using ethernet
pause frames to get senders to stop talking for a while. My understanding
was that this was on microsecond scale or even nanosecond time scales.
One of the mentions in the presentation was on slide 10 about
"fat-buffered router". In the data center, these are kind of going away,
because on-die memory is small and rates are high. A 64x100GE forwarding
asic might have 16MB of buffer, which is very little buffer for the kind
of bit rates we're talking here.
https://www.youtube.com/watch?v=sJMvAqEQCBE 1h44m in (proposed IEEE
802.1Qcz work) is the one I am thinking of.
Wonder how this would interact with the timing wheel proposed by Van
Jacobson?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2018-07-23 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 14:09 [Make-wifi-fast] " Dave Taht
2018-07-20 14:47 ` Luca Muscariello
2018-07-21 14:38 ` Jonathan Morton
2018-07-23 12:52 ` Mikael Abrahamsson [this message]
2018-07-23 15:36 ` [Make-wifi-fast] [Bloat] " Dave Taht
2018-07-23 17:26 ` dpreed
2018-07-21 13:19 ` 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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1807231444540.14354@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@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