I should have made that be an RFC. Ah, well.
On Thu, Jul 26, 2018 at 7:45 PM Dave Taht wrote:
>
> This patch restores cake's deployed behavior at line rate to always
> split gso, and makes gso splitting configurable from userspace.
>
> running cake unlimited (unshaped) at 1gigE, local traffic:
>
>
This patch restores cake's deployed behavior at line rate to always
split gso, and makes gso splitting configurable from userspace.
running cake unlimited (unshaped) at 1gigE, local traffic:
no-split-gso bql limit: 131966
split-gso bql limit: ~42392-45420
On this 4 stream test splitting gso a
I expect the first part of this patch to generate no controversy,
as being able to enable configure gso-splitting on or off in all
use cases of cake is a goodness.
But: I expect the single line re-enabling cake's fielded default of
always splitting gro and gso packets, in shaped or unshaped mode,
> On 27 Jul, 2018, at 12:09 am, Toke Høiland-Jørgensen wrote:
>
I haven't had time to try Cake in this context yet but hope to get to
that in the next couple months. I believe this will require one Cake
instance per-subscriber like we do with FQ-CoDel today.
>>>
>>> Yup, currently
Dave Taht 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
> stat
Dan Siemon writes:
> On Thu, 2018-07-26 at 19:42 +0200, Toke Høiland-Jørgensen wrote:
>> Dan Siemon writes:
>>
>> > I haven't had time to try Cake in this context yet but hope to get
>> > to
>> > that in the next couple months. I believe this will require one
>> > Cake
>> > instance per-subscri
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 expres
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
Typical academic paper testing with Reno.
At least they compared DCTCP
On Wed, Jul 25, 2018, 10:04 PM Dave Taht 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
>
On Thu, 2018-07-26 at 19:42 +0200, Toke Høiland-Jørgensen wrote:
> Dan Siemon writes:
>
> > I haven't had time to try Cake in this context yet but hope to get
> > to
> > that in the next couple months. I believe this will require one
> > Cake
> > instance per-subscriber like we do with FQ-CoDel t
On Thu, 2018-07-26 at 08:48 -0700, Dave Taht wrote:
> On Thu, Jul 26, 2018 at 8:46 AM Dan Siemon wrote:
> >
> > Tiny bit of self promotion here but Preseem (
> > https://www.preseem.com)
> > is a transparent bridge that leverages HTB/FQ-CoDel to make
> > subscriber plan enforcement provide much b
Dan Siemon writes:
> Tiny bit of self promotion here but Preseem (https://www.preseem.com)
> is a transparent bridge that leverages HTB/FQ-CoDel to make subscriber
> plan enforcement provide much better QoE. Leaving enforcement up to
> the deep queues in most network equipment has comparably very
On Thu, Jul 26, 2018 at 8:46 AM Dan Siemon wrote:
>
> Tiny bit of self promotion here but Preseem (https://www.preseem.com)
> is a transparent bridge that leverages HTB/FQ-CoDel to make subscriber plan
> enforcement provide much better QoE. Leaving enforcement up to the deep
> queues in most net
Tiny bit of self promotion here but Preseem (https://www.preseem.com)
is a transparent bridge that leverages HTB/FQ-CoDel to make subscriber plan
enforcement provide much better QoE. Leaving enforcement up to the deep queues
in most network equipment has comparably very bad results. We focus on W
14 matches
Mail list logo
