ingress bandwidth limitation for ipv6 is inaccurate

ingress bandwidth limitation for ipv6 is inaccurate

[yue longguang]

Hi,all

1.  according to my test,  bandwidth limitation is inaccurate for
ingress ipv6 .  The accuracy is affected by burst.   if rate is less
than 100mbit , set burst to 1MB or 2MB, the result is almost
acceptable.  but when rate is bigger , the result is approximately 1/3
of rate.
command:  tc filter add dev qr-869fbdc2-1e parent ffff: protocol ipv6
u32 match ip6 src any police rate 500mbit burst 1M drop
so except for using ifb, what should be done to get a accurate result.

2. can flowid option of  ingess's filter belong to egress's class.
for example    tc filter add dev qr-869fbdc2-1e parent ffff: protocol
ipv6 u32 match ip6 src any police rate 500mbit burst 1M flowid 1:10
 (1:10 classid  is egress's qdisc's class )

thank you for replying my two questions

ingress bandwidth limitation for ipv6 is inaccurate

[yue longguang]

Firstly, thank you  stephen.

Hi, kuznet:

1.  according to my test,  bandwidth limitation is inaccurate for
ingress ipv6 .  The accuracy is affected by burst.   if rate is less
than 100mbit , set burst to 1MB or 2MB, the result is almost
acceptable.  but when rate is bigger , the result is approximately 1/3
of rate.
command:  tc filter add dev qr-869fbdc2-1e parent ffff: protocol ipv6
u32 match ip6 src any police rate 500mbit burst 1M drop
so except for using ifb, what should be done to get a accurate result.

2. can flowid option of  ingess's filter belong to egress's class.
for example    tc filter add dev qr-869fbdc2-1e parent ffff: protocol
ipv6 u32 match ip6 src any police rate 500mbit burst 1M flowid 1:10
 (1:10 classid  is egress's qdisc's class )


thanks

Re: ingress bandwidth limitation for ipv6 is inaccurate

[yue longguang]

Hi, kuznet,i am looking forward to your reply.

thanks

On Tue, Oct 8, 2019 at 1:53 PM yue longguang <yuelongguang@gmail.com> wrote:
>
> Firstly, thank you  stephen.
>
> Hi, kuznet:
>
> 1.  according to my test,  bandwidth limitation is inaccurate for
> ingress ipv6 .  The accuracy is affected by burst.   if rate is less
> than 100mbit , set burst to 1MB or 2MB, the result is almost
> acceptable.  but when rate is bigger , the result is approximately 1/3
> of rate.
> command:  tc filter add dev qr-869fbdc2-1e parent ffff: protocol ipv6
> u32 match ip6 src any police rate 500mbit burst 1M drop
> so except for using ifb, what should be done to get a accurate result.
>
> 2. can flowid option of  ingess's filter belong to egress's class.
> for example    tc filter add dev qr-869fbdc2-1e parent ffff: protocol
> ipv6 u32 match ip6 src any police rate 500mbit burst 1M flowid 1:10
>  (1:10 classid  is egress's qdisc's class )
>
>
> thanks

Re: ingress bandwidth limitation for ipv6 is inaccurate

[David Miller]

From: yue longguang <yuelongguang@gmail.com>
Date: Sat, 12 Oct 2019 10:01:12 +0800

> Hi, kuznet,i am looking forward to your reply.

Targetting a specific developer, especially one who hasn't actually been active
in a very long time, is extremely unwise.

Please set your expectations appropriately.