Re: [Cake] Pre-print of Cake paper available

> On Apr 27, 2018, at 1:08 PM, Toke Høiland-Jørgensen wrote: >> >> I’ll leave it to you what to do with this information. Rough >> estimation: nat may be +2% CPU with rate limiting, and +15% without… > > Huh, that is maybe a bit much for a default; I guess it's better to just >

Re: [Cake] Pre-print of Cake paper available

Pete Heist writes: >> On Apr 25, 2018, at 10:28 PM, Toke Høiland-Jørgensen wrote: >> >> Hmm, actually it looks like just compiling against the conntrack code >> adds a module dependency on conntrack. And as far as I can tell, the >> code doesn't initiate any new

Re: [Cake] Pre-print of Cake paper available

David Lang writes: > On Tue, 24 Apr 2018, Toke Høiland-Jørgensen wrote: > >> Pete Heist writes: >> On Apr 24, 2018, at 7:58 AM, Jonathan Morton wrote: Turning NAT support on by default might actually be reasonable, since

Re: [Cake] Pre-print of Cake paper available

On Tue, 24 Apr 2018, Toke Høiland-Jørgensen wrote: Pete Heist writes: On Apr 24, 2018, at 7:58 AM, Jonathan Morton wrote: Turning NAT support on by default might actually be reasonable, since it doesn't really break anything if it's not needed - it

Re: [Cake] Pre-print of Cake paper available

On Tue, Apr 24, 2018 at 4:17 AM, Sebastian Moeller wrote: > That is true to some degree, but the overall algorithm is not that hard: Set the shaper at 50% of contracted rate and measure the bufferbloat (depending on the expertise of the user either via flent or the dslreports

Re: [Cake] Pre-print of Cake paper available

Sebastian Moeller writes: >> Looking at those threads, they seem to be increasing the number of >> queues. Not sure they need to, but, well, there's nothing in principle >> that says this couldn't be configurable (it is in FQ-CoDel). It would >> need a bit of a reorg of the

Re: [Cake] Pre-print of Cake paper available

Hi Toke, > On Apr 24, 2018, at 11:30, Toke Høiland-Jørgensen wrote: > > Sebastian Moeller writes: > [...] >>> >>> I don't think we can make assumptions on ISP deployments. >> >> Sure we do not really need to: >>

Re: [Cake] Pre-print of Cake paper available

> On Apr 24, 2018, at 11:15 AM, Toke Høiland-Jørgensen wrote: > > Well, you could use it on an ISP backhaul by having a separate CAKE > instance per customer, and having another mechanism to assign customer > traffic to each. Yep, am aware of that possibility, and the setup fun

Re: [Cake] Pre-print of Cake paper available

Sebastian Moeller writes: > Hi Toke, > > > >> On Apr 24, 2018, at 10:47, Toke Høiland-Jørgensen wrote: >> >> Sebastian Moeller writes: >> On Apr 24, 2018, at 01:01, Pete Heist wrote: > On Apr 23, 2018, at

Re: [Cake] Pre-print of Cake paper available

Hi Toke, > On Apr 24, 2018, at 10:47, Toke Høiland-Jørgensen wrote: > > Sebastian Moeller writes: > >>> On Apr 24, 2018, at 01:01, Pete Heist wrote: >>> >>> On Apr 23, 2018, at 10:39 AM, Toke Høiland-Jørgensen wrote:

Re: [Cake] Pre-print of Cake paper available

Pete Heist writes: >> On Apr 24, 2018, at 10:50 AM, Jonathan Morton wrote: >> >>> I think, if we wanted to support the ISP case, that a per-customer *shaper* >>> is more useful. >> >> Yes, I think the technology can be recoded to better suit a >>

Re: [Cake] Pre-print of Cake paper available

> On Apr 24, 2018, at 10:50 AM, Jonathan Morton wrote: > >> I think, if we wanted to support the ISP case, that a per-customer *shaper* >> is more useful. > > Yes, I think the technology can be recoded to better suit a multi-subscriber > environment; it would no longer

Re: [Cake] Pre-print of Cake paper available

> I think, if we wanted to support the ISP case, that a per-customer *shaper* > is more useful. Yes, I think the technology can be recoded to better suit a multi-subscriber environment; it would no longer be Cake, but would use some of the same key algorithms. - Jonathan Morton

Re: [Cake] Pre-print of Cake paper available

Sebastian Moeller writes: >> On Apr 24, 2018, at 01:01, Pete Heist wrote: >> >> >>> On Apr 23, 2018, at 10:39 AM, Toke Høiland-Jørgensen wrote: >>> >>> Last week we submitted an academic paper describing Cake. A pre-print is >>> now available

Re: [Cake] Pre-print of Cake paper available

Pete Heist writes: >> On Apr 23, 2018, at 10:39 AM, Toke Høiland-Jørgensen wrote: >> >> Last week we submitted an academic paper describing Cake. A pre-print is >> now available on arXiv: https://arxiv.org/abs/1804.07617 >> >> Comments welcome, of course :) > >

Re: [Cake] Pre-print of Cake paper available

> This (along with ’nat’) were part of an overall wish that ‘cake’ without any > keywords would do the “right thing” by default as often as possible Turning NAT support on by default might actually be reasonable, since it doesn't really break anything if it's not needed - it just eats a bit of

Re: [Cake] Pre-print of Cake paper available

> On Apr 24, 2018, at 1:31 AM, Jonathan Morton wrote: > >> Or since using the keywords would be fragile, is there a better way to know >> the proper sense for dual-srchost and dual-dsthost? > > This is covered in the tc-cake manage: … Oops, poor wording on my part. I

Re: [Cake] Pre-print of Cake paper available

> Last week we submitted an academic paper describing Cake. A pre-print is > now available on arXiv: https://arxiv.org/abs/1804.07617 > > Comments welcome, of course :) I just forwarded a link to my Canadian relatives who are involved in a rural community ISP. Lots of microwave links in the

[Cake] Pre-print of Cake paper available

Last week we submitted an academic paper describing Cake. A pre-print is now available on arXiv: https://arxiv.org/abs/1804.07617 Comments welcome, of course :) -Toke ___ Cake mailing list Cake@lists.bufferbloat.net