From: David Lang <david@lang.hm>
To: Mark Allman <mallman@icir.org>
Cc: Hal Murray <hmurray@megapathdsl.net>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] bufferbloat paper
Date: Tue, 8 Jan 2013 20:53:05 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1301082052000.21708@nftneq.ynat.uz> (raw)
In-Reply-To: <20130109015942.C08445B056C@lawyers.icir.org>
On Tue, 8 Jan 2013, Mark Allman wrote:
>>> Did any of their 90 homes contained laptops connected over WiFi?
>>
>> Almost certinly,
>
> Yeah - they nearly for sure did. (See the note I sent to bloat@ this
> morning.)
>
>> but if the connection from the laptop to the AP is 54M and the
>> connection from the AP to the Internet is 1G, you are not going to
>> have a lot of buffering taking place. You will have no buffering on
>> the uplink side, and while you will have some buffering on the
>> downlink side, 54M is your slowest connection and it takes a
>> significantly large amount of data in flight to fill that for seconds.
>
> 54Mbps *might* be your slowest link. It also could be somewhere before
> incoming traffic gets anywhere close to any of the CCZ gear. E.g., if
> the traffic is from my DSL line the bottleneck will be < 1Mbps and on my
> end of the connection.
Wait a min here, from everything prior to this it was sounding like you were in
a fiber-to-the-home experimental area that had 1G all the way to the houses, no
DSL involved.
Are we all minunderstanding this?
David Lang
> But, regardless, none of this matters for the results presented in the
> paper because our measurements factor out the local residences. Again,
> see the paper and the note I sent this morning. The measurements are
> taken between our monitor (which is outside the local homes) and the
> remote host somewhere out across the Internet. We are measuring
> wide-area and remote-side networks, not the local FTTH network.
>
> allman
>
>
>
>
next prev parent reply other threads:[~2013-01-09 4:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 19:03 Hal Murray
2013-01-08 20:28 ` Jonathan Morton
2013-01-09 0:12 ` David Lang
2013-01-09 1:59 ` Mark Allman
2013-01-09 4:53 ` David Lang [this message]
2013-01-09 5:13 ` Jonathan Morton
2013-01-09 5:32 ` Mark Allman
[not found] <87r4lvgss4.fsf@toke.dk>
2013-01-09 3:39 ` [Bloat] Bufferbloat Paper Mark Allman
2013-01-09 5:02 ` David Lang
2013-01-18 1:23 ` grenville armitage
-- strict thread matches above, loose matches on Subject: below --
2013-01-08 7:35 [Bloat] bufferbloat paper Ingemar Johansson S
2013-01-18 22:00 ` Haiqing Jiang
2013-01-07 23:37 [Bloat] Bufferbloat Paper Hagen Paul Pfeifer
2013-01-08 0:33 ` Dave Taht
2013-01-08 0:40 ` David Lang
2013-01-08 2:04 ` Mark Watson
2013-01-08 2:24 ` David Lang
2013-01-09 20:08 ` Michael Richardson
2013-01-08 4:52 ` Mark Watson
2013-01-08 1:54 ` Stephen Hemminger
2013-01-08 2:15 ` Oliver Hohlfeld
2013-01-08 12:44 ` Toke Høiland-Jørgensen
2013-01-08 13:55 ` Mark Allman
2013-01-09 0:03 ` David Lang
2013-01-10 13:01 ` Mark Allman
2013-01-09 20:14 ` Michael Richardson
2013-01-09 20:19 ` Mark Allman
2013-01-09 20:31 ` Michael Richardson
2013-01-10 18:05 ` Mark Allman
2013-01-08 14:04 ` Mark Allman
2013-01-08 17:22 ` Dave Taht
2013-01-09 20:05 ` Michael Richardson
2013-01-09 20:14 ` Mark Allman
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=alpine.DEB.2.02.1301082052000.21708@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=hmurray@megapathdsl.net \
--cc=mallman@icir.org \
/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