From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) (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 830242011CD for ; Wed, 11 Apr 2012 20:19:08 -0700 (PDT) Received: by werf13 with SMTP id f13so165115wer.16 for ; Wed, 11 Apr 2012 20:19:06 -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:content-transfer-encoding; bh=ZWDqYhqtBDqt11xRrsVGHR3wUIj6b3wgFUJSugGD20M=; b=zmUEmvHBrySEr5PH8vB8bsq+9Wt14UfT5H5h4dmw5e6D3wUw68YPRtYh8gOOUbFupn lDsAi46MsGDAhnbVvjjt4Wv6go+objV5K0JNFqne62QbSKmRYJiWEmMiamsMxRVGJYga vReJdOF1CbyaqVF/HwxlS2AAgr8xvzEGbxjofWT4YS2LF57Gc0eGk/Da+bNIfZMzkjWY 5SmhtyQMP/DDE3x4sTNx1rvigp0TbV4nGCFXuKllI0y0vhWTNJEOtqXTPHrbQj9/h9wM eOo81MpdHS7BWhl+iWK1kxMYc87Y2OEqQqLtkQhY0otxOne91Mp6WTh6sjwUbbp7pT8b Qf/w== MIME-Version: 1.0 Received: by 10.180.86.132 with SMTP id p4mr1873808wiz.15.1334200745950; Wed, 11 Apr 2012 20:19:05 -0700 (PDT) Received: by 10.223.127.194 with HTTP; Wed, 11 Apr 2012 20:19:05 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 Apr 2012 20:19:05 -0700 Message-ID: From: Dave Taht To: Christopher Sheats Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] CeroWRT for x86? 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: Thu, 12 Apr 2012 03:19:09 -0000 On Wed, Apr 11, 2012 at 7:23 PM, Christopher Sheats wro= te: > Hi, > > I'm looking to process 1Gbps, be it DDoS, Tor relay, or BitTorrent > traffic on a WAN port. Even though the WNDR3800 has a gigabit WAN > port, I'm not certain how successful it would be, especially with > sustained traffic and keeping the components cool. I have run sustained ipv4 traffic in excess of 440Mbit through the router for days at a time. That has been more (less firewall rules, more tuning, less bugs, les aqm), and less (ipv6 traffic, hefty aqms like qfq, etc). I don't have baseline numbers at present, we're still tuning. That said, I think your core applications requires more oomph. On the high end, octeon appears to be making some 100% open source product available that can scale easily to 10GigE. Certainly most x86 platforms today can saturate gigE with TSO/GSO off. > OpenWRT has an x86 > version, will CeroWRT? We have no plans for any other versions of cerowrt on any other hardware. There's no budget, no people, and no time for that. It is a platform for network research, and my hope is, when this release is done, to actually get some research done on top of it. The plan has always been to leverage x86 development by tracking the mainline kernel closely. Being able to innovate, test, and explore bufferbloat, ipv6, and security issues with two well understood 100% open source platforms (x86 servers, mips routers) and push (the good) code back into the mainline kernel, applications, and distributions such as openwrt, ubuntu, redhat, etc., is what we are trying to do. We get a lot of 'platform of the month' questions, and with our resources, doing merely two platforms has been a mighty stretch sometimes. Everything we do will end up upstream, in openwrt and elsewhere, or so we hope. In fact, it's generally easier to be working in the latest Linux kernels on x86, prototyping things that may or may not work on weaker hardware. The turn around times for new kernels and testing is substantially less, and the debugging tools vastly superior. As an example, the core new technologies in linux-3.3 relevant to bufferbloat (BQL, SFQ, SFQRED, QFQ) are in, linux-3.3 and can run on anything that can run 3.3. Last quarter we worked out of net-next on x86. Earlier this quarter the stuff that proved out landed in 3.3 A little bit later on, we got 3.3 running on mips, after doing a lot of backporting to 3.2 as 3.3 stabilized.... There's nearly nothing out of tree in cerowrt-3.3 at this time except some patches specific to the wndr3700 series of hardware, and a few ideas under test. As all the sources are available, please feel free to port cerowrt to x86, or just wait a month or two as the patches that prove out migrate upstream. But: Do give 3.3 a shot on a mainstream x86/x86_64 distribution with the debloat tool. AQM isn't just for routers anymore, but desktops, wireless clients, and servers. For more information, please see: http://europa.lab.bufferbloat.net/cerowrt/ (yes, this is a web page on a ro= uter) and the cerowrt-devel mailing list, and the cerowrt project wiki. > Thank you. De nada. > > -- > Christopher Sheats > yawnbox@gmail.com > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://www.bufferbloat.net