From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) by lists.bufferbloat.net (Postfix) with ESMTPS id 5EA283C9F0 for ; Mon, 18 Jan 2016 09:07:55 -0500 (EST) Received: by mail-yk0-x234.google.com with SMTP id a85so535833684ykb.1 for ; Mon, 18 Jan 2016 06:07:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=otvorenamreza-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=l9Zw3eRCEgeP8hHZdEOhWwygqxH5tmMCq9NOHI/yNeE=; b=ll4cEL8M65Qk6+sIgGOiY66vmrOM3zFLm3wgwsTgBpFPUSM5ru/W8fGx8pdG1UEJB1 cUWS+fRUj4S1fJPE85X76EcLn/516BUtxJ/jvqcrfUVtDG/JkgGBfxkfUMoB2aVF1i5h Qs5sF1LQYrwLqE3Zv7+O4AxDa815DjehKsV1xNjT5jt1Cn0FH7C0GOeYpvAiMnheL8yg 0z+xgix8Rn04FEKr0wfLntQFss0kkh3CX2353B9iBEK5I8Y+hF1dCbi2DGlaq/ow8dh0 IiVY58PTpN+gll9/89K5ORJ8rJgT1a8jLG0ptqTAIzadLNv2TohgiXQk55Yby8tM1m4P hncg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=l9Zw3eRCEgeP8hHZdEOhWwygqxH5tmMCq9NOHI/yNeE=; b=S9KhoyyCer99dd294kul/ve5+OUzKgTuNF3nsxS+8oGcdAuKfO6GQbUWrMAJuMhMXZ C75JU3XOLPT1OP3CAgYJEwM9c6bJUnaAJ0JUSsZOx/iMd8ZiSKfljvT2PqdCSfzYmzeJ zpeflej7oceBYrQj0p1Jl6zZQTvgFJMQB0F0cCZrggUvwusyA5QkABX/F7DwKtjQ+Ywa hPzJn2CX0xa4zw7upo4QVGV9KwhtGkX9Bl4m9bBbZJdxF8OLiJbJM4RYvPogezxaM0ln t9P9bejrc0JrAg/fq3CLun/aN5ijA51II26510sjZCnIzuBhCmp+0Z7H+yCSqFJwJjTy Db6Q== X-Gm-Message-State: ALoCoQkC87Fb5O5zouNldSohsRx56IQ3rNdNzzcTmtk/Q9sIxjm8M0R6kvGmRaLkJ6fsOqryZdWoLsDwin4l/yTmNuVzyJF4lg== X-Received: by 10.37.11.145 with SMTP id 139mr5212024ybl.0.1453126073733; Mon, 18 Jan 2016 06:07:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.114.7 with HTTP; Mon, 18 Jan 2016 06:07:14 -0800 (PST) X-Originating-IP: [93.141.157.81] In-Reply-To: References: <6737994D-CE0B-46F5-B55C-A584FF6A8014@gmail.com> From: Valent Turkovic Date: Mon, 18 Jan 2016 15:07:14 +0100 Message-ID: To: Jonathan Morton Cc: Outback Dingo , make-wifi-fast@lists.bufferbloat.net, "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cerowrt-devel] routers you can throw off the back of a truck X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 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, 18 Jan 2016 14:07:55 -0000 On Mon, Jan 18, 2016 at 12:29 PM, Jonathan Morton w= rote: > >> On 18 Jan, 2016, at 11:43, Valent Turkovic wr= ote: >> >> Can you please share your sqm qos script, or just how you invoke tc >> manually and I'll test it on my routers and see what happens then:) > > The autorate_ingress option is just a flag. Specify it after the bandwid= th parameter to give it a sane starting point, say 1Mbit. I think some of = the more recent GUIs have a field for =E2=80=9Cadvanced=E2=80=9D or =E2=80= =9Cexperimental=E2=80=9D options like this. Once it sees some traffic, it = should settle down reasonably quickly to the real link capacity, minus a sm= all margin to establish itself as the bottleneck. > > Eg: tc qdisc replace dev ifb0 root cake bandwidth 1Mbit autorate_ingress # tc qdisc replace dev eth0.2 root cake bandwidth 1Mbit autorate_ingress Unknown qdisc "cake", hence option "bandwidth" is unparsable So this is the reason I saw "bad" results when using cake... cake qdisc isn't even available in latest Chaos Chalmer... but Luci shows it as an option, really strange. Cake script [1] is located in /usr/lib/sqm/piece_of_cake.qos but there is no cake kernel module as far as I can see: # opkg list | grep sched kmod-sched - 3.18.20-1 - Extra kernel schedulers modules for IP traffic kmod-sched-connmark - 3.18.20-1 - Traffic shaper conntrack mark support kmod-sched-core - 3.18.20-1 - Core kernel scheduler support for IP traffic kmod-sched-esfq - 3.18.20-1 - Traffic shaper ESFQ support Again trough accidental discovery it looks like ESFQ [2] would also be an nice addition to codel. How about efq_codel insead of fq_codel ? Has anybody tried using ESFQ with codel? But back to OpenWrt... are there Cake packages for OpenWrt available anywhe= re? > As a reminder, autorate_ingress only works *downstream* of the bottleneck= link. Use it on the external interface=E2=80=99s *ingress* if possible. > I'll try this as soon as I get cake working on OpenWrt... >> From your presentation I see that if we had a daemon working in >> background and somehow measured tcp latency (how?) and then we could >> use it to raise/lower bandwidth limits on cake until we get best >> possible results. Ideally I would like to use a queueing mechanism >> that auto-configures everything. > > Right. The autorate_ingress feature works entirely in kernelspace, and e= ffectively takes care of the downstream half of the equation. The upstream = half turns out to be a much harder problem, because we can only measure the= uplink capacity when it is saturated, and typical consumer traffic doesn= =E2=80=99t do that very often. If we did have a saturating bulk upstream T= CP flow, then we could examine its RTT profile in userspace, under the assu= mption that the downlink was taken care of. > > One reasonable approach might be to use a userspace tool to periodically = scrape the downlink speed out of autorate_ingress, and set the uplink speed= to some fixed fraction of that (using tc qdisc change, for least disruptio= n). It might even make sense for 3G to inherently have such a ratio. If i= t does, does anyone know what it is? > >> @everybody any ideas how to tweak current "simple.qos" and >> "simplest.qos" scripts in OpenWrt for 3G and fiber optics? On fiber >> optic connection idle latency is around 30ms and on 3G connection is >> around 60ms, do I need to change 5ms default in fq_codel to these >> values? How? > > These are essentially internet-scale latencies, especially if you=E2=80= =99re just pinging the gateway immediately beyond the link, so the defaults= will work fine. The most recent versions of tc-adv include a set of intui= tive keywords to specify commonly-encountered RTT ranges; the one for =E2= =80=9Cinternet=E2=80=9D is 100ms, which corresponds to the Codel default pa= rameters. > > The 5ms figure is the target *queuing* latency, which should be considera= bly less than the estimated RTT; you really don=E2=80=99t want to be consis= tently adding 60ms of queuing on top of your 60ms inherent 3G latency. Thanks!