[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4e78ccb9-5983-f5f8-dded-0b193125c43a@gmail.com>
Date: Sun, 15 Sep 2019 11:37:53 -0600
From: David Ahern <dsahern@...il.com>
To: David Dai <zdai@...ux.vnet.ibm.com>, jhs@...atatu.com,
xiyou.wangcong@...il.com, jiri@...nulli.us, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: zdai@...ibm.com
Subject: Re: [v3] iproute2-next: police: support 64bit rate and peakrate in tc
utility
On 9/4/19 9:06 AM, David Dai wrote:
> For high speed adapter like Mellanox CX-5 card, it can reach upto
> 100 Gbits per second bandwidth. Currently htb already supports 64bit rate
> in tc utility. However police action rate and peakrate are still limited
> to 32bit value (upto 32 Gbits per second). Taking advantage of the 2 new
> attributes TCA_POLICE_RATE64 and TCA_POLICE_PEAKRATE64 from kernel,
> tc can use them to break the 32bit limit, and still keep the backward
> binary compatibility.
>
> Tested-by: David Dai <zdai@...ux.vnet.ibm.com>
> Signed-off-by: David Dai <zdai@...ux.vnet.ibm.com>
> ---
> Changelog:
> v1->v2:
> - Change patch submit component from iproute2 to iproute2-next
> - Move 2 attributes TCA_POLICE_RATE64 TCA_POLICE_PEAKRATE64 after
> TCA_POLICE_PAD in pkt_cls.h header to be consistent with kernel's
> pkt_cls.h header.
> v2->v3:
> - Use common functions of duparg and invarg in police filter.
> ---
> include/uapi/linux/pkt_cls.h | 2 +
> tc/m_police.c | 149 +++++++++++++++++++-----------------------
> tc/tc_core.c | 29 ++++++++
> tc/tc_core.h | 3 +
> 4 files changed, 102 insertions(+), 81 deletions(-)
>
applied to iproute2-next.
Powered by blists - more mailing lists