From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] I feel an urge to update this
Date: Thu, 25 Sep 2014 06:25:43 -0700 [thread overview]
Message-ID: <CAA93jw6byJ2Wcgx+Zz_FMp+sWAO1cxqjgZZOWqtO2KeqH-fwnw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409251459470.14735@uplift.swm.pp.se>
On Thu, Sep 25, 2014 at 6:00 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Thu, 25 Sep 2014, David Lang wrote:
>
>> What is the problem with making this assumption? Why should we try to
>> change every device on the Internet to provide this information instead of
>> just using this as the default?
>
> Read the email that started this thread.
One saving grace of the IW10 deployment so far is that it is (mostly)
limited to Linux, and that methods, such as pacing/initial
spreading/fq, to cope with it better, are developing concurrently.
It's not all bad - on GigE ethernet networks, it's ok, IW10 may well
be useful in wifi packet aggregation, etc, but it does do potentially
a great deal of damage to networks running at very low rates. My
concern has largely been the collateral damage it causes network
uploads from the edge, where vastly lower rates are common.
It could be mitigated further in a desktop deployment by (for example)
sticking with IW4 for everything going out a default gateway, and
steps taken to make sure applications like bittorrent/transmission
used a lower default. I have no idea what the IW is for android, but
that should perhaps be lower also. I think ledbat shouldn't have an IW
at all....
I would not mind if IW information was carried as a payload in dhcp/hnetd/etc...
I have no problem with people suggesting changes here that require
"changing the entire internet". We seem to have done that a couple
times, already. :) It would be nice if we could calculate the damage
it causes along whatever portion of the internet is running at below
10Mbit....
A simple question - how many T1 lines are left in the world?
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
--
Dave Täht
https://www.bufferbloat.net/projects/make-wifi-fast
next prev parent reply other threads:[~2014-09-25 13:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 23:33 Dave Taht
2014-09-20 9:03 ` Steinar H. Gunderson
2014-09-20 15:55 ` Jonathan Morton
2014-09-20 16:47 ` Michael Welzl
2014-09-23 5:48 ` Mikael Abrahamsson
2014-09-23 8:31 ` Jonathan Morton
2014-09-25 4:16 ` David Lang
2014-09-25 5:32 ` Mikael Abrahamsson
2014-09-25 7:35 ` David Lang
2014-09-25 8:08 ` Mikael Abrahamsson
2014-09-25 11:00 ` David Lang
2014-09-25 13:00 ` Mikael Abrahamsson
2014-09-25 13:25 ` Dave Taht [this message]
2014-09-25 14:35 ` Mikael Abrahamsson
2014-09-25 16:09 ` Rick Jones
2014-09-25 17:26 ` Mikael Abrahamsson
2014-09-25 17:49 ` Rick Jones
2014-09-27 8:59 ` Manolis Sifalakis
2014-09-29 17:28 ` Rick Jones
2014-10-04 19:56 ` Manolis Sifalakis
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=CAA93jw6byJ2Wcgx+Zz_FMp+sWAO1cxqjgZZOWqtO2KeqH-fwnw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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