From: Caleb Cushing <xenoterracide@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Dave Taht <dave.taht@gmail.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] lwn.net's tcp small queues vs wifi aggregation solved
Date: Thu, 21 Jun 2018 12:41:10 -0500 [thread overview]
Message-ID: <CAAHKNRHLFJ4rfLuovgyFN4aPVZjZkaJgKxs+fNQUOANd_nRpCg@mail.gmail.com> (raw)
In-Reply-To: <20180621084611.32f29234@xeon-e3>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
I'm not disagreeing, just saying that wifi is much more prevalent now than
just laptops... literally I only have a cord for emergency use
On Thu, Jun 21, 2018 at 10:46 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Thu, 21 Jun 2018 10:31:18 -0500
> Caleb Cushing <xenoterracide@gmail.com> wrote:
>
> > actually... all of my devices, including my desktop connect through wifi
> > these days... and only one of them isn't running some variant of linux.
> >
>
> Sigh. My experience with wifi is that it is not stable enough for that.
> Both AP's I have tried Linksys ACM3200 or Netgear WNDR3800 I still see
> random drop outs.
> Not sure if these are device resets (ie workarounds) or other issues.
>
> These happen independent of firmware (vendor, OpenWRT, or LEDE).
> So my suspicion is the that Wifi hardware is shite and that firmware is
> trying
> to workaround and mask the problem.
>
--
Caleb Cushing
http://xenoterracide.com
[-- Attachment #2: Type: text/html, Size: 1493 bytes --]
next prev parent reply other threads:[~2018-06-21 17:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 4:58 Dave Taht
2018-06-21 9:22 ` Toke Høiland-Jørgensen
2018-06-21 12:55 ` Eric Dumazet
2018-06-21 15:18 ` Dave Taht
2018-06-21 15:31 ` Caleb Cushing
2018-06-21 15:46 ` Stephen Hemminger
2018-06-21 17:41 ` Caleb Cushing [this message]
2018-06-21 15:50 ` Dave Taht
2018-06-21 16:29 ` David Collier-Brown
2018-06-21 16:54 ` Jonathan Morton
2018-06-21 16:43 ` Kathleen Nichols
2018-06-21 19:17 ` Dave Taht
2018-06-21 19:41 ` Sebastian Moeller
2018-06-21 19:51 ` Toke Høiland-Jørgensen
2018-06-21 19:54 ` Dave Taht
2018-06-21 20:11 ` Sebastian Moeller
2018-06-22 14:01 ` Kathleen Nichols
2018-06-22 14:12 ` Jonathan Morton
2018-06-22 14:49 ` Michael Richardson
2018-06-22 15:02 ` Jonathan Morton
2018-06-22 21:55 ` Michael Richardson
2018-06-25 10:38 ` Toke Høiland-Jørgensen
2018-06-25 23:54 ` Jim Gettys
2018-06-26 0:07 ` Jonathan Morton
2018-06-26 0:21 ` David Lang
2018-06-26 0:36 ` Simon Barber
2018-06-26 0:44 ` Jonathan Morton
2018-06-26 0:52 ` Jim Gettys
2018-06-26 0:56 ` David Lang
2018-06-26 11:16 ` Toke Høiland-Jørgensen
2018-06-26 1:27 ` Dave Taht
2018-06-26 3:30 ` Simon Barber
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=CAAHKNRHLFJ4rfLuovgyFN4aPVZjZkaJgKxs+fNQUOANd_nRpCg@mail.gmail.com \
--to=xenoterracide@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=stephen@networkplumber.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