From: jb <justin@dslr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] upgrade resync on osx cloud = massive bufferbloat for days
Date: Tue, 5 May 2015 22:44:45 +1000 [thread overview]
Message-ID: <CAH3Ss96vTxqs4Lfp9TH94J+SCyu6AyTPgugs-jzpBwd1Jg=wDA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5ocWueWega728Khsojumm9_ChERFm8g+7KqETmVKuuYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
It sounds like the problem is the broadcom chipset (earlier versions of)
combined with airdrop using the chipset to talk on two channels at the same
time,
which destroys wifi throughput. and not much to do with buffer bloat.
At least that is the TL;DR of a long article posted in the comments.
On Tue, May 5, 2015 at 4:50 PM, Dave Taht <dave.taht@gmail.com> wrote:
> http://garrett.damore.org/2015/05/macos-x-10103-update-is-toxic.html
>
> Jeeze, rich has been busy lately....
>
> --
> Dave Täht
> Open Networking needs **Open Source Hardware**
>
> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 1494 bytes --]
next prev parent reply other threads:[~2015-05-05 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 6:50 Dave Taht
2015-05-05 12:44 ` jb [this message]
2015-05-05 12:49 ` Rich Brown
2015-05-05 18:04 ` [Bloat] Sidebar on latency and "blip" David Collier-Brown
2015-05-05 21:54 ` Rich Brown
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='CAH3Ss96vTxqs4Lfp9TH94J+SCyu6AyTPgugs-jzpBwd1Jg=wDA@mail.gmail.com' \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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