From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: Van Jacobson <van@parc.com>,
bloat-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Please enter issues into the issue tracker - Issue system organisation needed.
Date: Thu, 24 Feb 2011 18:08:33 +0100 [thread overview]
Message-ID: <1298567313.2814.7.camel@edumazet-laptop> (raw)
In-Reply-To: <4D668827.8060508@freedesktop.org>
Le jeudi 24 février 2011 à 11:32 -0500, Jim Gettys a écrit :
> So we need better AQM algorithms and extensive testing: as you may have
> seen, SFB just went into the Linux mainline this morning.
>
Indeed ;)
> mtr on Linux is a step or
> two above old fashioned traceroute and ping. Steve Bauer knows how to
> modify traceroute/mtr to give us better ECN diagnosis. I'd love it if
> someone would take mtr under their wing and push it forward for both
> bufferbloat detection and ECN testing.
Not sure I understand here.
mtr could send ECN enabled frames to detect ECN blackholes, but since
ICMP replies wont have any ECN information, I cant see added value ?
next prev parent reply other threads:[~2011-02-24 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 14:19 Jim Gettys
2011-02-24 15:00 ` Fred Baker
2011-02-24 16:32 ` Jim Gettys
2011-02-24 17:08 ` Eric Dumazet [this message]
2011-02-24 18:31 ` Dave Täht
2011-02-24 19:29 ` Eric Dumazet
2011-02-25 10:12 ` [Bloat] smokeping for Windows Seth Teller
2011-02-25 10:51 ` Jim Gettys
2011-02-25 11:21 ` [Bloat] GSO (was: Please enter issues into the issue tracker - Issue system organisation needed) Jesper Dangaard Brouer
2011-02-25 11:54 ` Eric Dumazet
2011-02-25 15:48 ` Jesper Dangaard Brouer
2011-02-25 16:19 ` Eric Dumazet
2011-02-25 16:33 ` Eric Dumazet
2011-02-25 17:15 ` Jesper Dangaard Brouer
2011-02-26 2:41 ` [Bloat] GSO Dave Täht
2011-03-02 8:30 ` Jesper Dangaard Brouer
2011-03-04 2:23 ` Dave Täht
2011-02-25 15:40 ` [Bloat] Please enter issues into the issue tracker - Issue system organisation needed John W. Linville
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1298567313.2814.7.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=jg@freedesktop.org \
--cc=van@parc.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