From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 97FDB21F151 for ; Fri, 20 Dec 2013 13:01:57 -0800 (PST) Received: from hms-beagle-3.home.lan ([217.254.130.56]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MKHtm-1VtZVU3WEw-001kZ6 for ; Fri, 20 Dec 2013 22:01:54 +0100 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Sebastian Moeller In-Reply-To: Date: Fri, 20 Dec 2013 22:01:52 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <34E77F64-739C-49E4-B8A4-6ABBEAE4174B@gmail.com> <8DB84101-C942-49C4-99F0-6C9319961297@gmail.com> <22176178-A50F-48F2-A3A1-D3853764AD0E@gmail.com> <0E267F91-3CC8-48F4-92C0-AD8BACA98FCC@gmail.com> <1FA2FD44-D715-4B50-BB5A-BAF61070970B@gmx.de> <31B5B61B-4E58-4C5E-8F33-710CCE0918F4@gmail.com> <52B2D917.6080006@imap.cc> <52B2D93B.6050501@imap.cc> <52B2F63B.7060506@imap.cc> To: Dave Taht X-Mailer: Apple Mail (2.1510) X-Provags-ID: V03:K0:dJrgC5YWY4A1NgRp6209Rl16Y0RFqWGajHMD/bmjt0Wutsj89So Rk4p66kfuBidurHL8a36j3OgeG98m3cs/mDBX8dNEhvSLKFLCEPNoXZTr1pdHm+Xe0+1T4k OyTuJv8anpc5V/O3HR82yk5ifLCQNuAEFEVD5GQTNXuFJV5emfgV2/hU7Vr2r0F4AnUEhHk L3SKegFXvSJptIQ7UrfzA== Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] cerowrt-3.10.24-5 dev build released 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: Fri, 20 Dec 2013 21:01:58 -0000 Hi Dave, On Dec 20, 2013, at 19:01 , Dave Taht wrote: > I wanted to say how much I was enjoying catching up on this thread. >=20 > I think only one question came up for me during it, which is support > for a bfifo and pfifo qdisc? (if I missed something let me know ) > Support for these are darn useful for the research and I have long > meant to fold in the modified code I use for that. Byte limits are > very common for cable and dsl technologies and doing tests with > 64k,128k,256k, and 512k bfifos is quite revealing. (I have a ton of > plots lying about for this, I should put them up somewhere) >=20 > Sooo... I just checked in the limit stuff (untested) into aqm-scripts. > It requires that the limit option be dynamic and exposed to the gui, > and in the case of a bfifo is a byte limit rather than a packet limit. > There needs to be sane values for limit clamped somehow, as 1000 bytes > would be bad, and 512000 packets would be bad also. >=20 I just noticed we probably should go for ingress_Limit and = egress_Limit as there are different in simple_qos.sh, I assume for a = good reason=85 best sebastian > As for folding the selection of bfifo or pfifo into the gui, it's not > clear that we are doing "researcher mode", vs "mom mode" in a suitably > abstract way. Certainly I can imagine many a researcher wanting the > gui. >=20 > While I'm at it, there are some statistics like drops, and backlog, > etc, that a gui-ish interface might help. >=20 > polling tc -s qdisc show dev ge00 # and/or class show dev ge00 >=20 > I am curious if anyone is seeing the DMA tx error in 3.10.24-5? I have > one box that has now been up 4.4 days with no errors, but I haven't > pushed it. I'll be beating it up through the weekend and taking a look > at the gui work so far.