General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: Jonathan Morton <chromatix99@gmail.com>,
	Kathleen Nichols <nichols@pollere.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [aqm] ping loss "considered harmful"
Date: Mon, 2 Mar 2015 20:48:53 +0000	[thread overview]
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE93195E538@xmb-aln-x05.cisco.com> (raw)
In-Reply-To: <CAJq5cE20Vado=2tmsXzr5QYHq2yDUSd+mO2jMqZ3xxRBQFODng@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3170 bytes --]


While I do not formally speak for “a big vendor” in this (or any) context, I do happen to work for one.

There are several efforts underway within this particular big vendor to address bloat. Are these efforts crash programs to get code out the door as fast as humanly possible? No. There are efforts underway, though. These things take time…… To be frank, the best way to drive feature development/deployment/adoption in most big companies is to have customers ask for them.

We are actually starting to see broader awareness of the problem at the SP network edge, and this is probably where we need solutions the fastest. There have been some gap-filler changes in the HFC space recently, and the next generation CMTS products will have a quite robust solution. As noted previously, the CPE and the DSLAMs will also need to be addressed. Unfortunately (perhaps fortunately to some folks on this list…. but I digress), the company I work for is no longer in these parts of the business, as we sold off the Linksys group off a few years ago and got out of the DSLAM business many years ago. I do still have some contacts in the chipset vendor community in the CPE space, and could help drive awareness if it would help. As most of us understand, the chipset vendors have a lot clout in this area - as they supply most of the heavy lifting code to the OEM/ODM CPE folks for their commercial offers. The open source community is currently ahead of the chipset folks and the OEM/ODM folks in this space.

So, IMHO the best way to make progress in the CPE arena is to get the chipset vendors to provide a robust AQM scheme in their default drivers. There may have to be some tweaks to get a given algorithm to work in a given chipset/memory/CPU architecture. In fact, there may be room for algorithms that take advantage of features of a given chipset, or to design a new chipset that “does the right thing” in uCode.  If I were a consultant – this is where I would focus my efforts……….

I am not sure how to crack the DSLAM egg, though. Different set of players, different set of initial conditions.

Bill VerSteeg











From: bloat-bounces@lists.bufferbloat.net [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Jonathan Morton
Sent: Monday, March 02, 2015 2:42 PM
To: Kathleen Nichols
Cc: bloat
Subject: Re: [Bloat] [aqm] ping loss "considered harmful"


Probably the least cynical answer to that I can come up with is the hope that big vendors get a clue that this stuff is needed, and start hiring field experts as consultants to help them get it right.

You can stop snickering now.

Another possibility is that some of us have to club together and make our own hardware that Does The Right Thing, possibly still based on one of the generic reference hardware platforms, if we can find one that we like and is cheap enough to compete. Which, once again, would take care of the CPE problem but practically nothing else, unless we somehow managed to get a foot in the door of the DSLAM market. Which is about as likely as the Prince of Darkness taking a skiing holiday at home.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 9167 bytes --]

  reply	other threads:[~2015-03-02 20:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  3:57 [Bloat] " Dave Taht
2015-03-02  4:05 ` [Bloat] [aqm] " Mikael Abrahamsson
2015-03-02  4:06 ` [Bloat] [Cerowrt-devel] " David Lang
     [not found] ` <7B3E53F5-2112-4A50-A777-B76F928CE8F2@trammell.ch>
2015-03-02 10:17   ` [Bloat] [aqm] " Mikael Abrahamsson
2015-03-02 10:54     ` Jonathan Morton
2015-03-02 12:44       ` [Bloat] [Cerowrt-devel] " dpreed
2015-03-02 19:01       ` [Bloat] " Kathleen Nichols
2015-03-02 19:41         ` Jonathan Morton
2015-03-02 20:48           ` Bill Ver Steeg (versteb) [this message]
2015-03-02 22:15             ` Dave Taht
     [not found]     ` <34374.1425365125@turing-police.cc.vt.edu>
2015-03-04  8:14       ` [Bloat] [Cerowrt-devel] " Mikael Abrahamsson
     [not found]   ` <54F4DBC9.1010700@isi.edu>
2015-03-02 23:14     ` [Bloat] " David Lang
     [not found]       ` <54F4F166.6040303@isi.edu>
2015-03-02 23:34         ` David Lang
     [not found] ` <E8355113905631478EFF04F5AA706E9830B5875D@wtl-exchp-2.sandvine.com>
     [not found]   ` <CAPRuP3n0tbFKJyPwpr3ntb7abXgyRRhtH23aeeYzvj9mgj_G8g@mail.gmail.com>
2015-03-02 18:36     ` [Bloat] [Cerowrt-devel] " David Lang
     [not found] ` <md2fsa$o1s$1@ger.gmane.org>
2015-03-02 20:38   ` [Bloat] " Dave Taht
2015-03-04  8:12     ` Mikael Abrahamsson
     [not found]   ` <E8355113905631478EFF04F5AA706E9830B5923E@wtl-exchp-2.sandvine.com>
2015-03-02 20:39     ` David Lang
2015-03-03 17:20 ` Fred Baker (fred)
2015-03-03 17:29   ` Wesley Eddy
2015-03-03 18:00     ` Fred Baker (fred)
2015-03-04  5:24       ` Dave Taht
2015-03-05 18:56         ` Curtis Villamizar
2015-03-05 19:50           ` Rich Brown
2015-03-04 17:34       ` [Bloat] [Cerowrt-devel] " dpreed
2015-03-04 19:45         ` [Bloat] [aqm] [Cerowrt-devel] " Mikael Abrahamsson
2015-03-05 22:27           ` Sam Silvester
2015-03-05 20:38 ` [Bloat] " Matt Taggart
2015-03-05 20:53   ` 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=AE7F97DB5FEE054088D82E836BD15BE93195E538@xmb-aln-x05.cisco.com \
    --to=versteb@cisco.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=nichols@pollere.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