From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] fq in p4
Date: Thu, 26 Jul 2018 23:11:50 +0200 [thread overview]
Message-ID: <87r2jp1z3d.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4X5K4901NeCk9FB-BV6YTvtipH4CJ8txFWJqG3v-ofng@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> writes:
> 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..."
Yeah, the lack of any interface to the queueing in p4 always bothered
be. Good to see that is (hopefully) being worked on :)
-Toke
prev parent reply other threads:[~2018-07-26 21:11 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
2018-07-26 21:11 ` Toke Høiland-Jørgensen [this message]
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=87r2jp1z3d.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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