Re: [RFC PATCH] sch_htb: Hierarchical QoS hardware offload

2020-07-14 Thread Maxim Mikityanskiy
On 2020-07-08 09:44, Cong Wang wrote: On Fri, Jun 26, 2020 at 3:46 AM Maxim Mikityanskiy wrote: HTB doesn't scale well because of contention on a single lock, and it also consumes CPU. Mellanox hardware supports hierarchical rate limiting that can be leveraged by offloading the functionality o

Re: [RFC PATCH] sch_htb: Hierarchical QoS hardware offload

2020-07-07 Thread Cong Wang
On Fri, Jun 26, 2020 at 3:46 AM Maxim Mikityanskiy wrote: > > HTB doesn't scale well because of contention on a single lock, and it > also consumes CPU. Mellanox hardware supports hierarchical rate limiting > that can be leveraged by offloading the functionality of HTB. True, essentially because

Re: [RFC PATCH] sch_htb: Hierarchical QoS hardware offload

2020-07-07 Thread Maxim Mikityanskiy
Comments are very welcome before I move to the full implementation. On 2020-06-26 13:46, Maxim Mikityanskiy wrote: This patch is a follow-up for the RFC posted earlier [1]. You can find a detailed description of the motivation there, and this patch is RFC code that shows possible implementation.

[RFC PATCH] sch_htb: Hierarchical QoS hardware offload

2020-06-26 Thread Maxim Mikityanskiy
This patch is a follow-up for the RFC posted earlier [1]. You can find a detailed description of the motivation there, and this patch is RFC code that shows possible implementation. The main changes are in net/sched/sch_htb.c file, and this patch also contains stubs for mlx5 that show the driver AP