From: David Ahern <dsahern@gmail.com>
To: David Dai <zdai@linux.vnet.ibm.com>,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: zdai@us.ibm.com
Subject: Re: [v3] iproute2-next: police: support 64bit rate and peakrate in tc utility
Date: Sun, 15 Sep 2019 11:37:53 -0600 [thread overview]
Message-ID: <4e78ccb9-5983-f5f8-dded-0b193125c43a@gmail.com> (raw)
In-Reply-To: <1567609611-27051-1-git-send-email-zdai@linux.vnet.ibm.com>
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@linux.vnet.ibm.com>
> Signed-off-by: David Dai <zdai@linux.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.
prev parent reply other threads:[~2019-09-15 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 15:06 [v3] iproute2-next: police: support 64bit rate and peakrate in tc utility David Dai
2019-09-15 17:37 ` David Ahern [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e78ccb9-5983-f5f8-dded-0b193125c43a@gmail.com \
--to=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=zdai@linux.vnet.ibm.com \
--cc=zdai@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox