From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id F26712021DD for ; Sun, 8 Dec 2013 02:40:31 -0800 (PST) Received: from hms-beagle-3.home.lan ([87.150.22.181]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M9NIY-1ViTz81zHa-00CgSj for ; Sun, 08 Dec 2013 11:40:28 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Sebastian Moeller In-Reply-To: <87haakx1ev.wl%jch@pps.univ-paris-diderot.fr> Date: Sun, 8 Dec 2013 11:40:31 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <09D8F3A0-7172-4677-9887-119813E28740@gmx.de> References: <20131203222559.GV8066@einstein.kenyonralph.com> <7ieh5pew2d.wl%jch@pps.univ-paris-diderot.fr> <87haakx1ev.wl%jch@pps.univ-paris-diderot.fr> To: Juliusz Chroboczek X-Mailer: Apple Mail (2.1510) X-Provags-ID: V03:K0:ivd67BZjTXsX+AQUm47HECD5S/c8P2UIrNmzur9cGZ/xiUNxl0M DS9g90FO3Loz+9Z/3HdL3yRYPOgMm3cRNIboupn3Rae40wJNNHgZccIkOwi2F5qs59CZFOp O6LOwmwV/dyHk6WV4xDk1CmmowNL+IR+1FR5rAetqF+ypSpvwa8hcAfZwd58ZYdsW0eHnj6 x7CmYtAIo0cCC2VnHdRKg== Cc: bloat Subject: Re: [Bloat] curious..... 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: Sun, 08 Dec 2013 10:40:32 -0000 Hi Juliusz, On Dec 7, 2013, at 13:59 , Juliusz Chroboczek = wrote: >>> Perhaps you should push your system to OpenWRT? >=20 >> There is still some work going on to streamline the gui. >=20 > Fair enough. That's important. >=20 >> there are less features in the aqm-scripts for prioritizing packet >> types than qos-scripts. >=20 > I wouldn't bother much with that. The promise of fq_codel is that we > can get rid of our prioritising hacks -- if we need that kind of > features, then fq_codel has failed. Is that really true? given enough concurrent flows, critical = flows might be delayed purely be the round robin scheduling of equally = "worthy" packets in fq_codel, so some residual priory system might still = make sense... >=20 >> I just had to come up with a way to disable it at high (> 80 mbit) >> rates on incoming traffic (not enough cpu in cerowrt), >=20 > I wouldn't bother with that either. 120 Mbit/s is the highest rate = you > can get in Europe as far as I can tell, so being able to push 80 = Mbit/s > on a four year old router is fine (as long as you're careful to avoid > shaping traffic between LAN and WLAN -- I certainly wouldn't want > backing up my laptop to be capped at 80 Mbit/s). mmmh, currently in Germany residential fiber tops out at = 200Mbit/s, cable at 150, and VDSL tops out at 50Mbit/s. Next year cable = companies promised 200Mbit/s and the biggest VDSL provider = promised100Mbit/sec (G.993.5 Vectoring). So, the wndr3[7,8]00 are = getting a bit long in the tooth. What would be a reasonable replacement, anybody any good ideas? @Dave: for the one tier shaper, maybe using TBF instead of HTB = will allow higher shaping rates? (I happily admit , I have no clue which = part of HTB is the expensive one, the token bucket filter or the = hierarchy.) >=20 >> so I'd like it to run faster, maybe using drr in that case, or >> something like what free.fr uses... >=20 > What are they using? >=20 >> And there are actually two aqm/packet scheduling shapers in there (a >> simple 1 tier and a 3 tier one), >=20 > Remove the non-default features. Be a man, Dave, dump it all. Being more cautious, not to say cowardly, I would opt for hiding = the non-default features :) Kidding aside, what should be the default? >=20 >> In the interim, existing openwrt users can add ceropackages-3.3 into >> their feeds. >=20 > They won't. If you want to have an effect on the world, you need to > push it into the default OpenWRT scripts. Best Regards Sebastian >=20 > -- Juliusz > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat