Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] tc coding comments
Date: Thu, 19 Nov 2015 12:05:40 +0000	[thread overview]
Message-ID: <564DBB14.2040801@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw4y0yqWXRRsVX0Jz3o8Wegy6OAvgggK159P6DyVXyRbEA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]



On 19/11/15 08:56, Dave Taht wrote:
> tc qdisc add dev whatever root cake bandwidth 50gbit does not work
Grins.  I was sort of looking at this yesterday.  It's a 32 bit integer
'limit' within tc.  tc works in bits per second, but what it passes to
kernel is bytes per second (>>3)  So the 32bit netlink API interface can
potentially cope with 34359738360 bits per second(2^32 -1 * 8),
unfortunately tc's get_rate() can only cope with 4294967295 (2^32 -1)
bits per second.  get_rate64() would solve that along with a 64bit
netlink api rate path.

A quick look at iproute2 master reveals netem, tbf & htb as the only
users so far of get_rate64()




[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]

      parent reply	other threads:[~2015-11-19 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  8:56 Dave Taht
2015-11-19 11:03 ` Sebastian Moeller
2015-11-19 11:11 ` Kevin Darbyshire-Bryant
2015-11-19 11:15   ` Toke Høiland-Jørgensen
2015-11-19 11:25     ` Kevin Darbyshire-Bryant
2015-11-19 12:05 ` Kevin Darbyshire-Bryant [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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=564DBB14.2040801@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    /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