Jonas Mårtensson <martensson.jo...@gmail.com> writes: > On Wed, Apr 11, 2018 at 7:15 PM, Toke Høiland-Jørgensen <t...@toke.dk> > wrote: > >> Jonathan Morton <chromati...@gmail.com> writes: >> >> >> On 11 Apr, 2018, at 6:24 pm, Toke Høiland-Jørgensen <t...@toke.dk> >> wrote: >> >> >> >> So, um, did we cram so many features into Cake that it no longer uses >> >> less CPU? Can anyone confirm these results? >> > >> > To be sure about this, it seems wise to configure Cake to turn off as >> > many of the new features as possible. That means selecting "besteffort >> > flows nonat" mode at least. >> > >> > I forget whether simplest.qos correctly uses the built-in shaper with >> > Cake, rather than just layering it with HTB as usual. If not, then of >> > course Cake will use more CPU, and we should be grateful that it's by >> > a relatively small margin (maybe 15%). >> >> It is definitely using Cake as the shaper; in besteffort mode, but with >> nat and triple-isolation enabled I think. I'll run another test tomorrow >> with those disabled. > > > Is there any difference between using simplest.qos and piece_of_cake.qos > when Cake is used as qdisc?
Not really, no. piece_of_cake understands the zero_dscp_ingress option, simplest.qos does not. I think that is the only difference. I just used simplest.qos because that made it easier to switch between fq_codel and cake ;) -Toke _______________________________________________ Cake mailing list Cake@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cake
