From: Kathleen Nichols <nichols@pollere.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fixing bufferbloat in 2017
Date: Mon, 28 Nov 2016 09:52:03 -0800 [thread overview]
Message-ID: <0bdf0f65-1101-fa99-ef33-4c23db9266a1@pollere.com> (raw)
In-Reply-To: <20161128085856.23ddfd70@samsung9.wavecable.com>
Well, it would be good to know where the congestion is coming from, i.e.
saying that "the network is congested" doesn't say which network. Since
our downlink got upgraded, there is rarely an issue there but from time
to time the comcast network just "goes down" in that it seems that
nothing gets out (the Nextdoor list then pops up all these postings "is
anyone else having internet problems?") but this is infrequent. We've
been able to find all sorts of interesting things in the home network
including some substandard cabling (which has been replaced) and various
wifi oddities (which would be easier to characterize if I could get
better data on the clients, particularly wrt to Google wifi but I have
an idea on this....)
Guess if your house is on fire, you stop watching the cat videos, right?
Kathie
On 11/28/16 8:58 AM, Stephen Hemminger wrote:
> My experience has been that the media and developer attention span is
> short lived, and maybe that is part of the problem. Gaming is a niche
> market, and therefore is easily ignored; plus the classic gaming
> market is dying and I am not sure anyone is really investing in it.
>
> The current hot topic use case seems to be machine learning and voice
> interaction. I wonder if we could build a use case something related
> to that? "Ok Google, my house is on fire!!" -- "Sorry can not call
> fire department, network is congested".
>
>
> _______________________________________________ Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
next prev parent reply other threads:[~2016-11-28 17:52 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` Rich Brown
2016-11-27 1:53 ` Aaron Wood
2016-11-27 6:10 ` Mikael Abrahamsson
2016-11-27 21:24 ` Dave Taht
2016-11-28 2:11 ` Kathleen Nichols
2016-11-28 2:16 ` Jim Gettys
2016-11-28 6:00 ` Jan Ceuleers
2016-11-28 12:48 ` David Collier-Brown
2016-11-28 15:12 ` Dave Taht
2016-11-28 15:23 ` Wesley Eddy
2016-11-28 15:35 ` Dave Taht
2016-11-28 16:58 ` Stephen Hemminger
2016-11-28 17:07 ` Dave Taht
2016-11-28 19:02 ` Jonathan Morton
2016-11-28 17:52 ` Kathleen Nichols [this message]
2016-11-28 15:14 ` Pedro Tumusok
2016-11-28 15:23 ` Dave Taht
2016-11-28 15:10 ` Dave Taht
2016-11-28 2:47 ` David Lang
[not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` [Bloat] fixing " Rich Brown
2016-11-23 18:46 ` David Lang
2016-11-23 18:58 ` Jonathan Morton
2016-11-23 19:15 ` David Lang
2016-11-23 20:37 ` Toke Høiland-Jørgensen
2016-11-22 15:32 Dave Taht
2016-11-22 16:19 ` Jan Ceuleers
2016-11-22 16:25 ` Dave Taht
2016-11-22 16:38 ` Jim Gettys
2016-11-23 8:28 ` Mikael Abrahamsson
2016-11-23 11:04 ` Jonathan Morton
2016-11-23 11:59 ` Kelvin Edmison
2016-11-23 13:31 ` Pedro Tumusok
2016-11-23 14:05 ` Mário Sérgio Fujikawa Ferreira
2016-11-23 17:20 ` Mikael Abrahamsson
2016-11-23 17:27 ` Benjamin Cronce
2016-11-23 17:31 ` Mikael Abrahamsson
2016-11-23 17:40 ` Sebastian Moeller
2016-11-23 17:50 ` Noah Causin
2016-11-23 17:56 ` David Lang
2016-11-23 18:05 ` Benjamin Cronce
2016-11-23 18:38 ` David Lang
2016-11-23 19:29 ` Benjamin Cronce
2016-11-23 19:42 ` David Lang
2016-11-23 20:20 ` Dave Taht
2016-11-23 17:54 ` David Lang
2016-11-23 18:09 ` Mikael Abrahamsson
2016-11-23 18:18 ` Sebastian Moeller
2016-11-23 18:24 ` Dave Taht
2016-11-23 20:39 ` Toke Høiland-Jørgensen
2016-11-23 19:13 ` David Lang
2016-11-23 18:17 ` Dave Taht
2016-11-23 15:32 ` Pedretti Fabio
2016-11-23 19:29 ` Stephen Hemminger
2016-11-23 19:22 ` Dave Taht
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=0bdf0f65-1101-fa99-ef33-4c23db9266a1@pollere.com \
--to=nichols@pollere.com \
--cc=bloat@lists.bufferbloat.net \
/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