From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lpp01m010-f43.google.com (mail-lpp01m010-f43.google.com [209.85.215.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id DC5A42012AC; Tue, 8 May 2012 18:04:52 -0700 (PDT) Received: by lagr15 with SMTP id r15so10275944lag.16 for ; Tue, 08 May 2012 18:04:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=WxebzAyTUVuB+3/qPjcZ2ElDlWjq/sPvfMNuyQF/aIE=; b=J+eN/54+qqegpLR7rf1iT58i19saaXGlJDeZnHqUKutMiaxPleYhk8H+dNh5yNw7il vCpsCx8Beif5bXBB+SanxW1+VpQl7PHJHMV63+btuefbWnNR97iI+Tg+5eRm/yo0G5s+ xZz2gX1sSSFRmXQ4r8QFOFYBBo3F4TPt4Fkg3Uy1vPZI2Xp0yNLrh6t/HNv6H1IrWPPf KucCcInduLFixYrxvxU0QYaaAzOfCnH5pS9c9QH1yPMkA44k8B6b2j4OBSzi4VVKuol9 ZIBTDBcm8IaAaKN7LBY1tFSmyLR0HZwj5Ej6XYW6Pg0eeO8qfJPf1iFbdIUeRa5pXE9l QEZg== MIME-Version: 1.0 Received: by 10.112.27.228 with SMTP id w4mr9861679lbg.5.1336525490489; Tue, 08 May 2012 18:04:50 -0700 (PDT) Received: by 10.112.132.98 with HTTP; Tue, 8 May 2012 18:04:50 -0700 (PDT) Date: Tue, 8 May 2012 18:04:50 -0700 Message-ID: From: Dave Taht To: bloat , codel@lists.bufferbloat.net Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: [Codel] The challenge X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 01:04:53 -0000 Both the acm queue article and jim's blog entry this morning were way above mensa's standards. Nobody has attempted to explain the elegant simplicity of the algorithm itself in the inverse sqrt however! I have a good grip on it, and am trying, but can barely explain it to myself. Anyone else care to dig through the codel code and try to put it into english? Nice bit in ReadWrite News: http://www.readwriteweb.com/enterprise/2012/05/good-news-for-solving-buffer= bloat-codel-provides-no-knobs-solution.php Bob Cringley lays down the challenge for us here on the bloat list, and details the opportunity. http://www.cringely.com/2012/05/beginning-of-the-end-for-bufferbloat/ He closes with: "My advice to Cisco, Netgear, D-Link and others is that this could be an important moment in their businesses if they choose to approach it correctly. It=92s a chance to get all of us to buy new routers, perhaps new everything. Think of the music industry bonanza when we all shifted our record libraries from vinyl to CDs. It could be the same for networking equipment. But for that to happen the vendors have to finally acknowledge bufferbloat and use their marketing dollars to teach us all why we should upgrade ASAP. Everybody would win. Take our money, please." With the cerowrt project, at least, I've hoped to make that shift possible, and to some extent... happen. We have *working code*, and *proof of concept*. What's next? Where do we go from here? --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://www.bufferbloat.net