General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: "Eggert, Lars" <lars@netapp.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] sigcomm wifi
Date: Wed, 20 Aug 2014 18:05:57 -0400	[thread overview]
Message-ID: <CAGhGL2Cb9fFnhVEkhPDhaf3dj4zBJmYB_WPc3+RaAZ9_+aC5wQ@mail.gmail.com> (raw)
In-Reply-To: <91696A3A-EF44-4A1A-8070-D3AF25D0D9AC@netapp.com>

[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]

On Wed, Aug 20, 2014 at 3:12 AM, Eggert, Lars <lars@netapp.com> wrote:

> On 2014-8-19, at 18:45, Dave Taht <dave.taht@gmail.com> wrote:
> > I figured y'all would be bemused by the wifi performance in the sigcomm
> > main conference room this morning...
> >
> > http://snapon.lab.bufferbloat.net/~d/sigcomm_tuesday.png
>
> There is a reason we budgeted a 1G uplink for SIGCOMM Helsinki and made
> sure we had sufficient AP coverage...
>

​And what kinds of AP's?  All the 1G guarantees you is that your bottleneck
is in the wifi hop, and they can suffer as badly as anything else
(particularly consumer home routers).

The reason why 802.11 works ok at IETF and NANOG is that:
  o) they use Cisco enterprise AP's, which are not badly over buffered.  I
don't have data on which enterprise AP's are overbuffered.
  o) they do a good job of placing the AP's, given a lot of experience
  o) they turn on RED in the router, which, since there is a lot of
aggregated traffic, can actually help rather than hurt, and keep TCP
decently policed.
  o) they play some interesting diffserv marking tricks to prioritize some
traffic, getting part of the effect the fq_codel gives you in its "new
flow" behavior by manual configuration.  Fq_codel does much better without
having to mess around like this.

Would be nice if they (the folks who run the IETF network) wrote a BCP on
the topic; I urged them some IETF's ago, but if others asked, it would help.

If you try to use consumer home routers running factory firmware and hack
it yourself, you will likely lose no matter what you backhaul is (though
you might do ok using current CeroWrt/OpenWrt if you know what you are
doing.
                                  -- Jim


> Lars
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>

[-- Attachment #2: Type: text/html, Size: 3690 bytes --]

  parent reply	other threads:[~2014-08-20 22:05 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 16:45 Dave Taht
2014-08-20  7:12 ` Eggert, Lars
2014-08-20 14:01   ` Dave Taht
2014-08-20 22:05   ` Jim Gettys [this message]
2014-08-21  6:52     ` Eggert, Lars
2014-08-21  7:11       ` Michael Welzl
2014-08-21  8:30         ` David Lang
2014-08-22 23:07           ` Michael Welzl
2014-08-22 23:50             ` David Lang
2014-08-23 19:26               ` Michael Welzl
2014-08-23 23:29                 ` Jonathan Morton
2014-08-23 23:40                   ` Steinar H. Gunderson
2014-08-23 23:49                     ` Jonathan Morton
2014-08-24  1:33                   ` David Lang
2014-08-24  2:29                     ` Jonathan Morton
2014-08-24  5:12                       ` David Lang
2014-08-24  6:26                         ` Jonathan Morton
2014-08-24  8:24                           ` David Lang
2014-08-24  9:20                             ` Jonathan Morton
2014-08-25  7:25                             ` Michael Welzl
2014-08-30  7:20                             ` Jonathan Morton
2014-08-31 20:46                               ` Simon Barber
2014-08-25  7:35                   ` Michael Welzl
2014-08-24  1:09                 ` David Lang
2014-08-25  8:01                   ` Michael Welzl
2014-08-25  8:19                     ` Sebastian Moeller
2014-08-25  8:33                       ` Michael Welzl
2014-08-25  9:18                         ` Alex Burr
2014-08-31 22:37                       ` David Lang
2014-08-31 23:09                         ` Simon Barber
2014-09-01  0:25                           ` David Lang
2014-09-01  2:14                             ` Simon Barber
2014-08-31 22:35                     ` David Lang
2014-08-21  6:56     ` David Lang
2014-08-21  7:04     ` David Lang
2014-08-21  9:46       ` Jesper Dangaard Brouer
2014-08-21 19:49         ` David Lang
2014-08-21 19:57           ` Steinar H. Gunderson
2014-08-22 17:07             ` Jan Ceuleers
2014-08-22 18:27               ` Steinar H. Gunderson
2014-08-21  8:58     ` Steinar H. Gunderson
2014-08-22 23:34       ` David Lang
2014-08-22 23:41         ` Steinar H. Gunderson
2014-08-22 23:52           ` David Lang
2014-08-22 23:56             ` Steinar H. Gunderson
2014-08-23  0:03               ` Steinar H. Gunderson
2014-08-21  9:23     ` Mikael Abrahamsson
2014-08-21  9:30       ` Steinar H. Gunderson
2014-08-22 23:30         ` David Lang
2014-08-22 23:40           ` Steinar H. Gunderson
2014-08-20  8:30 ` Steinar H. Gunderson
2014-08-21  6:58   ` David Lang
2014-08-24  3:49 Hal Murray
2014-08-24  3:52 ` Jonathan Morton
2014-08-24  5:14 ` David Lang
2014-08-25  7:43   ` Michael Welzl

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=CAGhGL2Cb9fFnhVEkhPDhaf3dj4zBJmYB_WPc3+RaAZ9_+aC5wQ@mail.gmail.com \
    --to=jg@freedesktop.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=lars@netapp.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