netdev - Re: maximal supported bit rate in traffic control

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAFS8XSX6OPCanVu8CjNEaQ-WEr1tum_P0s5=uQuAo3UJMcxuVg@mail.gmail.com>
Date:   Tue, 15 May 2018 10:25:20 +0300
From:   Eitan Raviv <eraviv@...hat.com>
To:     netdev@...r.kernel.org
Cc:     Eric Dumazet <eric.dumazet@...il.com>,
        Dan Kenigsberg <danken@...hat.com>
Subject: Re: maximal supported bit rate in traffic control

Thanks a lot for the fast reply.
However we are using HFSC, and I did not find a 64bit HFSC qdisc. Does
one exits?
If not, are there plans to create one?

Thank you

On Tue, May 15, 2018 at 1:26 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
>
>
> 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.
>