From: David Lang <david@lang.hm>
To: Etienne Champetier <champetier.etienne@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Dual Channel Wi-Fi
Date: Thu, 12 Sep 2019 23:03:24 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1909122301110.6081@qynat-yncgbc> (raw)
In-Reply-To: <CAOdf3gr7uxuLhYksnvt_SZ14Q8NShNpDnONbj0b2ZAYpQ6BDsw@mail.gmail.com>
it's an optimization that will work well when there is only one person using the
network, and utterly collapse when there is a lot of use.
it assumes that 'high priority' and bulk things only move in one direction, it
uses more channels, which will cause more collisions with other users and other
networks.
a fairly typical type of idea to someone who doesn't look at what's actually
happening at the RF level.
David Lang
On Fri, 13 Sep 2019, Etienne Champetier wrote:
> Date: Fri, 13 Sep 2019 14:47:38 +0900
> From: Etienne Champetier <champetier.etienne@gmail.com>
> To: bloat <bloat@lists.bufferbloat.net>
> Subject: [Bloat] Dual Channel Wi-Fi
>
> I'm curious what people on this mailing list think about this Wi-Fi
> optimisation
>
> https://www.cablelabs.com/technologies/dual-channel-wi-fi
> https://github.com/openwrt/packages/pull/9972
>
next prev parent reply other threads:[~2019-09-13 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 5:47 Etienne Champetier
2019-09-13 6:01 ` Dave Taht
2019-09-13 6:03 ` David Lang [this message]
2019-09-13 6:13 ` Dave Taht
2019-09-13 7:18 ` Dave Taht
2019-09-13 9:13 ` Sebastian Moeller
2019-09-13 11:58 ` Toke Høiland-Jørgensen
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=nycvar.QRO.7.76.6.1909122301110.6081@qynat-yncgbc \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=champetier.etienne@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