On 8/27/19 10:53 PM, Dave Taht wrote: > > Although this is very cool, I think in this case the OP is being > a router, not server? This mechanism is generic. EDT has not been designed for servers only. One HTB class (with one associated qdisc per leaf) per rate limiter does not scale, and consumes a _lot_ more memory. We have abandoned HTB at Google for these reasons. Nice thing with EDT is that you can stack arbitrary number of rate limiters, and still keep a single queue (in FQ or another layer downstream)
- Re: Unable to create htb tc classes more than 64K Akshat Kakkar
- Re: Unable to create htb tc classes more tha... Cong Wang
- Re: Unable to create htb tc classes more... Akshat Kakkar
- Re: Unable to create htb tc classes ... Akshat Kakkar
- Re: Unable to create htb tc classes ... Cong Wang
- Re: Unable to create htb tc clas... Akshat Kakkar
- Re: Unable to create htb tc... Cong Wang
- Re: Unable to create htb tc... Eric Dumazet
- Re: Unable to create htb tc... Toke Høiland-Jørgensen
- Re: Unable to create htb tc... Dave Taht
- Re: Unable to create htb tc... Eric Dumazet
- Re: Unable to create htb tc classes ... Jesper Dangaard Brouer