General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Mirja Kühlewind" <mirja.kuehlewind@tik.ee.ethz.ch>
Cc: "cheshire@apple.com" <cheshire@apple.com>,
	"iccrg@irtf.org" <iccrg@irtf.org>,
	"Bob Briscoe \(bob.briscoe@bt.com\)" <bob.briscoe@bt.com>,
	Ingemar Johansson S <ingemar.s.johansson@ericsson.com>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>,
	"ietf@trammell.ch" <ietf@trammell.ch>
Subject: Re: [Bloat] ECN issues
Date: Thu, 25 Jun 2015 10:49:48 -0700	[thread overview]
Message-ID: <CAA93jw5YiTeyJMKKezsay=_3jDRoeUw526UePjjyAsLKBHJ+pA@mail.gmail.com> (raw)
In-Reply-To: <04ED8D23-53C3-4F12-9647-3A07FFB43352@tik.ee.ethz.ch>

In my case I just managed to show that congestive (rather than path)
loss can be a factor in the reliability of even a low rate, CS6
prioritized, link local multicast routing protocol (babel), over
present day linux wifi, even using a modern fq+aqm+ecn system.

Enabling ECN markings in babel and watching for CEs while under load, here:

http://snapon.lab.bufferbloat.net/~d/newrouters/linuxcap.cap

I am not sure where to go with that, but I am deploying it at a small
scale anyway, as gathering link local rtt information somewhat
passively at the moment and point of congestion is important to guide
my other work on wifi. No plans for a paper or presentation, it was
just "interesting", let me know if you have any ideas in addition to
this

http://lists.alioth.debian.org/pipermail/babel-users/2015-April/001974.html

as to where to go with it.

  parent reply	other threads:[~2015-06-25 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 11:34 Ingemar Johansson S
2015-06-24 11:48 ` Hagen Paul Pfeifer
     [not found] ` <04ED8D23-53C3-4F12-9647-3A07FFB43352@tik.ee.ethz.ch>
2015-06-25 17:49   ` Dave Taht [this message]
2015-06-25 18:15     ` Jonathan Morton
2015-06-25 18:52       ` David Lang
2015-06-26 11:05       ` Juliusz Chroboczek
2015-06-25 19:02   ` Ingemar Johansson S
2015-06-25 22:07     ` Jonathan Morton
     [not found]     ` <6D65AC6E-4AA1-4F8C-B758-D63EEC59A0E2@tik.ee.ethz.ch>
2015-07-19  8:21       ` [Bloat] [iccrg] " Scheffenegger, Richard

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='CAA93jw5YiTeyJMKKezsay=_3jDRoeUw526UePjjyAsLKBHJ+pA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=bob.briscoe@bt.com \
    --cc=cheshire@apple.com \
    --cc=iccrg@irtf.org \
    --cc=ietf@trammell.ch \
    --cc=ingemar.s.johansson@ericsson.com \
    --cc=mirja.kuehlewind@tik.ee.ethz.ch \
    /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