From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] fq in p4
Date: Thu, 26 Jul 2018 11:49:08 -0700 [thread overview]
Message-ID: <CAA93jw4X5K4901NeCk9FB-BV6YTvtipH4CJ8txFWJqG3v-ofng@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4N6_+Vjj7DCCKdWzsGo6qvX-hCAkS67LS=+XXQi7T23A@mail.gmail.com>
some word from avind's group.
"Thanks Dave for the pointer! Sounds very interesting, so we will
definitely take a look.
We do have p4 code for AFQ and happy to send it your way. There are
two crucial components to the AFQ implementation -- one is the switch
state stuff and that is easily expressed in p4, and the other is the
queue scheduling stuff which p4 currently doesn't provide any
knobs/mechanisms for realizing it. But there are some upcoming
Barefoot mechanisms that can help us directly realize the necessary
mechanism (i.e., the rotating priority queue mechanism as described in
the paper) and we do think that the queue scheduling disciplines would
eventually make its way into standard p4 in some time..."
and
"Thanks for all of the pointers, especially the VJ talk! We are in
fact working on timer wheels and calendar queues as a scheduling
primitive to ensure timely delivery of messages at the application
level -- for example, we can use such mechanisms to ensure low tail
latency for key-value requests and/or map-reduce co-flows.
We will get you the code and do go ahead and forward our work/emails
to the mailing lists."
my editorial comment: JOY. BLISS. RAPTURE. There is light at the end
of this tunnel.
On Thu, Jul 26, 2018 at 11:33 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> well, they got a working in-hardware prototype, and a p4
> implementation, it uses DRR, shows feasability
> if nothing else. (they also report big wins throughout, and their aqm
> works against flow isolation).
>
> Happy. I asked them if they had any code we can play with.
>
> On Thu, Jul 26, 2018 at 11:17 AM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > Typical academic paper testing with Reno.
> > At least they compared DCTCP
> >
> > On Wed, Jul 25, 2018, 10:04 PM Dave Taht <dave.taht@gmail.com> wrote:
> >>
> >> https://homes.cs.washington.edu/~arvind/papers/afq.pdf
> >>
> >> --
> >>
> >> Dave Täht
> >> CEO, TekLibre, LLC
> >> http://www.teklibre.com
> >> Tel: 1-669-226-2619
> >> _______________________________________________
> >> Cake mailing list
> >> Cake@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/cake
>
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-07-26 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 5:04 Dave Taht
2018-07-26 18:17 ` Stephen Hemminger
2018-07-26 18:33 ` Dave Taht
2018-07-26 18:49 ` Dave Taht [this message]
2018-07-26 21:11 ` Toke Høiland-Jørgensen
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=CAA93jw4X5K4901NeCk9FB-BV6YTvtipH4CJ8txFWJqG3v-ofng@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=stephen@networkplumber.org \
/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