netdev - Re: [PATCH net] cxgb4: fix Tx multi channel port rate limit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 19 Jan 2020 16:12:22 +0100 (CET)
From:   David Miller <davem@...emloft.net>
To:     rahul.lakkireddy@...lsio.com
Cc:     netdev@...r.kernel.org, nirranjan@...lsio.com, vishal@...lsio.com,
        dt@...lsio.com
Subject: Re: [PATCH net] cxgb4: fix Tx multi channel port rate limit

From: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
Date: Fri, 17 Jan 2020 18:23:55 +0530

> T6 can support 2 egress traffic management channels per port to
> double the total number of traffic classes that can be configured.
> In this configuration, if the class belongs to the other channel,
> then all the queues must be bound again explicitly to the new class,
> for the rate limit parameters on the other channel to take effect.
> 
> So, always explicitly bind all queues to the port rate limit traffic
> class, regardless of the traffic management channel that it belongs
> to. Also, only bind queues to port rate limit traffic class, if all
> the queues don't already belong to an existing different traffic
> class.
> 
> Fixes: 4ec4762d8ec6 ("cxgb4: add TC-MATCHALL classifier egress offload")
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>

Applied.