From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] start at interval handling
Date: Mon, 12 Oct 2015 02:47:59 +0300 [thread overview]
Message-ID: <B15EFEF5-0871-42DD-BF24-396BF00ED699@gmail.com> (raw)
In-Reply-To: <CAA93jw5mL_68QBtAwXjhTwzgVGRMf+dWXOfdfs=qJvTiKjr2tg@mail.gmail.com>
> On 12 Oct, 2015, at 00:30, Dave Taht <dave.taht@gmail.com> wrote:
>
> so... anyway, this does start some api breakage, also. Anyone else got
> braincells?
Some of that is definitely wrong. The rate_overhead parameter needs to be signed, for a start, since some last-mile encapsulations have *less* overhead than Ethernet. That’s why I had it as ‘short’ instead of ‘u16’.
- Jonathan Morton
next prev parent reply other threads:[~2015-10-11 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 21:30 Dave Taht
2015-10-11 23:47 ` Jonathan Morton [this message]
2015-10-12 7:55 ` Dave Taht
2015-10-12 8:01 ` Loganaden Velvindron
2015-10-14 1:50 ` Benjamin Cronce
2015-10-14 2:12 ` Dave Taht
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=B15EFEF5-0871-42DD-BF24-396BF00ED699@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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