From: Jim Gettys <jg@freedesktop.org>
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] uplink_buffer_adjustment
Date: Tue, 25 Feb 2014 11:46:25 -0500 [thread overview]
Message-ID: <CAGhGL2Bv1Co6DEprsZZnqXbL9Q6N+RVPApb-x2GA88JeNzgUBw@mail.gmail.com> (raw)
In-Reply-To: <D82FF87B-F220-45B4-AA87-27037DB472C9@icsi.berkeley.edu>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Tue, Feb 25, 2014 at 11:02 AM, Nicholas Weaver <nweaver@icsi.berkeley.edu
> wrote:
>
> On Feb 25, 2014, at 7:59 AM, Jim Gettys <jg@freedesktop.org> wrote:
> > So it is arguably a "bug" in netalyzr. It is certainly extremely
> misleading.
> >
> > Nick?
>
> Rewriting it as a TCP-based stresser is definatly on our to-do list.
>
Good; though I'm not sure you'll be able to build a TCP one that fills the
buffers fast enough to determine some of the buffering out there (at least
without hacking the TCP implementation, anyway).
The other piece of this is detecting flow queuing being active; this makes
a bigger difference to actual latency than mark/drop algorithms do by
themselves.
- Jim
>
>
> --
> Nicholas Weaver it is a tale, told by an idiot,
> nweaver@icsi.berkeley.edu full of sound and fury,
> 510-666-2903 .signifying nothing
> PGP: http://www1.icsi.berkeley.edu/~nweaver/data/nweaver_pub.asc
>
>
[-- Attachment #2: Type: text/html, Size: 2079 bytes --]
next prev parent reply other threads:[~2014-02-25 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 11:14 Oliver Niesner
2014-02-25 12:08 ` Sebastian Moeller
2014-02-25 14:05 ` Maciej Soltysiak
2014-02-25 14:19 ` Sebastian Moeller
2014-02-25 15:59 ` Jim Gettys
[not found] ` <D82FF87B-F220-45B4-AA87-27037DB472C9@icsi.berkeley.edu>
2014-02-25 16:46 ` Jim Gettys [this message]
2014-02-25 21:27 ` dpreed
2014-02-25 17:10 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGhGL2Bv1Co6DEprsZZnqXbL9Q6N+RVPApb-x2GA88JeNzgUBw@mail.gmail.com \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=nweaver@icsi.berkeley.edu \
/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