From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake byte limits too high by 10x
Date: Fri, 29 May 2015 15:36:59 +0300 [thread overview]
Message-ID: <CAJq5cE2+TN-U5E1F5jeoB1GLAXaFVtQRdDFJqnpA6WL5VeH-=w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw60SFUP4BObBwCOy88nc5_jfykGK=45+09V+MMN0kNkyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
> being number of flow sensitive
I still don't entirely understand what you mean by this. It's already flow
number sensitive because it operates per flow - for N saturated flows it'll
initially send N signals per interval - and it gets more so every time I
find a way to improve the flow isolation.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 393 bytes --]
next prev parent reply other threads:[~2015-05-29 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 5:14 Dave Taht
2015-05-25 4:47 ` Jonathan Morton
2015-05-25 19:46 ` Dave Taht
2015-05-29 12:24 ` Jonathan Morton
2015-05-29 12:36 ` Jonathan Morton [this message]
2015-05-29 13:02 ` Jonathan Morton
2015-05-29 17:49 ` 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='CAJq5cE2+TN-U5E1F5jeoB1GLAXaFVtQRdDFJqnpA6WL5VeH-=w@mail.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