From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) (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 E76A721F112 for ; Sun, 5 Jan 2014 19:29:48 -0800 (PST) Received: by mail-wg0-f53.google.com with SMTP id k14so15094360wgh.8 for ; Sun, 05 Jan 2014 19:29:47 -0800 (PST) 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=xAWRM2hE7yZd906B9ts1vGBdRCgBdYHNJUFXOdWEUdU=; b=pf8w+dYnZP6dcOunfep7ANcRa+Q7JJsSy6w2KJcTDbPXJsp3EATg23igdTBSvP7P0c v7Bdi1gPYXmBjKq3QOooxwhfWpmdrB6qRs+ygpstu6K8DGO8M3ydgiEKzrzGc5pcDibK BrLf5fhLA0oBDKs3GnRp39mAy01AzWO7jKHaaw8SaLhGjdU5Yc9RtoGxRVBpS7mTWIIW ovdREovmOxs7F93xwtTxO1yfPfr/NmxFKD0DjL3cU/YB2rN4G9GCIzNauOCtH8thd33p g9qAFHfBmVoze5rDaUw7V5lh1rdtECQYV+TVrjljbG7AfTGxSVM68WjW86kRAJtI0YO9 /8Ig== MIME-Version: 1.0 X-Received: by 10.180.37.69 with SMTP id w5mr10514607wij.53.1388978987115; Sun, 05 Jan 2014 19:29:47 -0800 (PST) Received: by 10.217.123.69 with HTTP; Sun, 5 Jan 2014 19:29:47 -0800 (PST) In-Reply-To: <52C855B1.1040209@imap.cc> References: <01558084-B7D8-448A-A4ED-CE36D18AAA97@gmail.com> <52C855B1.1040209@imap.cc> Date: Sun, 5 Jan 2014 19:29:47 -0800 Message-ID: From: Dave Taht To: Fred Stratton Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] SQM Question #5: Link Layer Adaptation Overheads X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jan 2014 03:29:55 -0000 On Sat, Jan 4, 2014 at 10:40 AM, Fred Stratton wrote= : > Link Names: > > For consistency, if ADSL is used as a portmanteau term, them VDSL should = be > used as the equivalent for VDSL and VDSL2. > > CeroWRT has to decide whether it is an experimental build, or something t= hat > will eventually be used in production, so these decisions can be made > consistently. Well, what I was aiming for was for us to get the sqm scripts and gui up to where they were better than the standard openwrt qos scripts and then push them up to openwrt to where they could be more widely deployed. Aside from being able to dynamically assign priorities in the gui, we are there. Except that nfq_codel is currently getting better results than fq_codel at low bandwidths, and I'm tempted to pour all of simple.qos into C. As for cero's future - certainly since all the snowden revelations I've been going around saying that "friends don't let friends run factory firmware". I would like a stable build of sqm and cerowrt to emerge, and to then go off and work on improving wifi. Regrettably what seems to be happening is more backwards than forwards on the former, and ramping up on the ath9k and ath10k is taking more time than I'd like, and it seems likely I'll be working on those primarily on another platform and only eventually pushing the results out to cero, mainline kernel So it's still at the "keep plugging away" point for sqm, ipv6, cero in general, with the stable release always just out of sight. Tackling the ipv6 problem is next on my agenda on cero, and getting a test suite going is next on my day job. > I concur with your ADSL setup suggestion as default. I have been running = the > Sebastian Moeller ping script overnight to calculate ADSL overhead for th= e > last several days. After several hours of curve fitting using Octave, an > overhead result is displayed. This novel approach works well. It would be nice to get to where we could autoconfigure a router using tools like these with no human intervention. This includes bandwidth estimation. > The overhead for the particular setup I use was 40 for PPPoE, and 10 for > PPPoA. > > The default you suggest is a suitable starting point, I suggest. > > > On 04/01/14 18:16, Rich Brown wrote: >> >> QUESTION #5: I still don=92t have any great answers for the Link Layer >> Adaptation overhead descriptions and recommendations. In an earlier mess= age, >> (see >> https://lists.bufferbloat.net/pipermail/cerowrt-devel/2013-December/0019= 14.html >> and following messages), Fred Stratton described the overheads carried b= y >> various options, and Sebastian Moeller also gave some useful advice. >> >> After looking at the options, I despair of giving people a clear >> recommendation that would be optimal for their equipment. Consequently, = I >> believe the best we can do is come up with =93good enough=94 recommendat= ions >> that are not wrong, and still give decent performance. >> >> In this spirit, I have changed Draft #3 of the =93Setting up SQM=94 page= to >> reflect this understanding. See >> http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_AQM_for_Cero= Wrt_310 >> >> ADSL/ATM link: Choose =93ADSL/ATM", and set Per Packet Overhead = to >> 40 >> VDSL2 link: Choose =93VDSL=94, and set Per Packet Overhead to 8 >> Other kind of link (e.g., Cable, Fiber, Ethernet, other not >> listed): Choose =93None (default)=94, and set Per Packet Overhead to 0 >> >> NB: I have changed the first menu choice to =93ADSL/ATM=94 and the secon= d to >> =93VDSL=94 in the description. I would ask that we change to GUI to refl= ect >> those names as well. This makes it far easier/less confusing to talk abo= ut >> the options. >> >> As always, I welcome help in setting out clear recommendations that work >> well for the vast majority of people who try CeroWrt. Thanks. >> >> Rich >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html