From: yue longguang <yuelongguang@gmail.com>
To: kuznet@ms2.inr.ac.ru, stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: ingress bandwidth limitation for ipv6 is inaccurate
Date: Sat, 12 Oct 2019 10:01:12 +0800 [thread overview]
Message-ID: <CAPaK2r-38JUpdZqhKWsY22C85ZHMJD3H4QEHkRd_TSKMFwMURQ@mail.gmail.com> (raw)
In-Reply-To: <CAPaK2r_T28BqvOkjDSD=SR-5sKeD_HgHu1tvB+b1jR20FuU0WQ@mail.gmail.com>
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
next prev parent reply other threads:[~2019-10-12 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 5:53 ingress bandwidth limitation for ipv6 is inaccurate yue longguang
2019-10-12 2:01 ` yue longguang [this message]
2019-10-12 3:27 ` David Miller
2019-10-13 7:17 yue longguang
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=CAPaK2r-38JUpdZqhKWsY22C85ZHMJD3H4QEHkRd_TSKMFwMURQ@mail.gmail.com \
--to=yuelongguang@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.