From: Luca Muscariello <luca.muscariello@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Bloat] [Make-wifi-fast] Van Jacobson's slides on timing wheels at netdevconf
Date: Fri, 20 Jul 2018 16:47:00 +0200 [thread overview]
Message-ID: <CAHx=1M707THPD1FoD+V=9BdVBKYVbzDX09t7yrdoA4hGVcXH6g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7fzv+pe2CiD6YOZ_n=7zH2XjFW=HaFypbm=B-1OLraXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
and C) you can implement any packet scheduler using a timing wheel using
virtual times.
On Fri, Jul 20, 2018 at 4:09 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> https://www.files.netdevconf.org/d/46def75c2ef345809bbe/files/?p=/Evolving%20from%20AFAP%20%E2%80%93%20Teaching%20NICs%20about%20time.pdf
>
> Talking about replacing queues with timing wheels.
>
> I will refrain from commenting other than noting A) I like it. We
> essentially have limits in the OS on packet scheduling that make it
> harder and harder to have sub 2ms, much less sub 10usec, queues with
> the existing qdiscs and pacing systems B) that NIC support seems
> needed. I can think of a lot of things I'd like to have in a NIC
> (which certainly include default timestamping on rx and multiple kinds
> of X-tuple hash) - but hadn't thought about replacing queues entirely!
>
> I haven't read up on carousel yet either.
>
> Look forward to seeing the video when it comes out.
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
[-- Attachment #2: Type: text/html, Size: 1978 bytes --]
next prev parent reply other threads:[~2018-07-20 14:47 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 ` Luca Muscariello [this message]
2018-07-21 14:38 ` [Bloat] [Make-wifi-fast] " Jonathan Morton
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='CAHx=1M707THPD1FoD+V=9BdVBKYVbzDX09t7yrdoA4hGVcXH6g@mail.gmail.com' \
--to=luca.muscariello@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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