From: Eric Dumazet <eric.dumazet@gmail.com>
To: Eitan Raviv <eraviv@redhat.com>, netdev@vger.kernel.org
Subject: Re: maximal supported bit rate in traffic control
Date: Mon, 14 May 2018 15:26:58 -0700 [thread overview]
Message-ID: <f5797c00-f51f-430c-abf8-db1762f8a993@gmail.com> (raw)
In-Reply-To: <CAFS8XSVwgZd=FXrfzKzNuc0OiRwn+qQu7Uq3WkCp5AT4gYD5Tw@mail.gmail.com>
On 05/14/2018 03:15 PM, Eitan Raviv wrote:
> Hi,
>
> In RHEVM we use traffic control to enable users to shape their QoS on
> the networks they use.
>
> IIUC from the traffic control man page, the maximal bit rate currently
> supported (RHEL 7.4) is 2^32 - 1 bytes per sec, which translates to 32
> Gibit\s if I have done my maths correctly.
>
> Does anyone know whether there are any plans to support larger bit
> rate values upstream or downstream soon or at all?
>
At least 3 qdisc got 64bit rates :
HTB ( TCA_HTB_RATE64 ), tbf ( TCA_TBF_RATE64), netem ( TCA_NETEM_RATE64 )
No plans yet for others.
next prev parent reply other threads:[~2018-05-14 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 22:15 maximal supported bit rate in traffic control Eitan Raviv
2018-05-14 22:26 ` Eric Dumazet [this message]
2018-05-15 7:25 ` Eitan Raviv
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=f5797c00-f51f-430c-abf8-db1762f8a993@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=eraviv@redhat.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox