General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Koen Holtman <k.holtman@chello.nl>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Bulk] Re: Motivating commercial entities? tell the sales manager (fwd)
Date: Mon, 9 Mar 2015 09:29:53 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1503090926140.20507@uplift.swm.pp.se> (raw)
In-Reply-To: <alpine.DEB.2.00.1503082045210.1571@noodle>

On Sun, 8 Mar 2015, Koen Holtman wrote:

> One thing that I am unclear on is whether the codel algorithms are mature 
> enough to allow them to be pitched as a low-risk solution that Wi-Fi vendors 
> could all adopt to fix bufferbloat. If I browse around I am getting a

There are two things that the wifi vendors need to do, one is related to 
bufferbloat, the other is not.

They need to make sure the drivers for their devices give enough support 
for the IP stack of the device to be able to handle bufferbloat.

They need to make sure multicast works much better than it does today. 
IPv6 relies on it.

If they can't fix this, then more people are going to rely on their cabled 
connections because wifi won't be good enough, and I would imagine this 
will make it less of a driver to upgrade their equipment to support newer 
Wifi standards, which sounds like that would hurt sales. If they do fix 
it, then whatever new standard they come up with will drive sales because 
now Wifi will work better and there would be a driver to upgrade for the 
userbase, for instance that they can watch multicast TV on their wifi 
(which plain doesn't work today).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2015-03-09  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 20:46 Koen Holtman
2015-03-09  8:29 ` Mikael Abrahamsson [this message]
2015-03-09 15:40   ` David Lang
2015-03-09 15:43     ` Steinar H. Gunderson
2015-03-09 16:04       ` David Lang
2015-03-10  7:03     ` Mikael Abrahamsson

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.1503090926140.20507@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=k.holtman@chello.nl \
    /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