From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 752A321F611 for ; Sat, 6 Jun 2015 08:50:52 -0700 (PDT) Received: by obcej4 with SMTP id ej4so21867078obc.0 for ; Sat, 06 Jun 2015 08:50:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vn8d8TG5Wa6+GTTXDDx1FPeMLOngBRe/CIX1vzSPNdE=; b=mDCZm45oQXeChgz4ly0bqNN/YUL15hRvJCiGGrDHReNw4gv+gaKQdP0eMUf51M4I8B BA6Kuk0OZlcOJY1LR3b/Of1ycpzrhSaNzHMldLotO0XLzArhrIbsQ5AcSZu91E26wZnM 3onk+BY32kMnWni5LRh6eIE6QE0vsulypXtMq8s8MzgDDCJAEE9EB2ZQEfu4cU3jazyK A2XBO74HqEAhUhkFhmbrHBY6CO9l0yNeAPEhviOFfe7/TJNIIUlvx7Xsdx+9dczoQapU zsJo7fOBFho6s1GULRRcz2CSGK0KLAi5X75i5aNfEvUsLfjrfwPGSuK9FKxHs7N4aY98 KRhw== MIME-Version: 1.0 X-Received: by 10.60.60.70 with SMTP id f6mr7475600oer.8.1433605852368; Sat, 06 Jun 2015 08:50:52 -0700 (PDT) Received: by 10.202.105.129 with HTTP; Sat, 6 Jun 2015 08:50:52 -0700 (PDT) In-Reply-To: <557315CC.1060405@darbyshire-bryant.me.uk> References: <5572F7E0.3060602@darbyshire-bryant.me.uk> <0A0D06AB-CC83-4D99-80C6-8E7822C8707C@gmx.de> <557315CC.1060405@darbyshire-bryant.me.uk> Date: Sat, 6 Jun 2015 08:50:52 -0700 Message-ID: From: Dave Taht To: Kevin Darbyshire-Bryant Content-Type: text/plain; charset=UTF-8 Cc: bloat Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2015 15:51:21 -0000 I have long been on a quest to find a debloatable dsl driver, and a box we could recomend to end users to use that could use hard, rather than soft, rate limiting in this case. I think we could dig up resources to tear something binary-ish apart at this point.