From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 D0B5E21F779 for ; Mon, 12 Oct 2015 02:24:56 -0700 (PDT) Received: by oiak8 with SMTP id k8so58429210oia.1 for ; Mon, 12 Oct 2015 02:24:55 -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=vDGRSEuBX4ts4gduKFoxJ8NqpRpTXgk8ge7LuYIv6rA=; b=JD2m4pU6IOaH67RFi0s4LTKzvByzChFPkjr6e20gyteew44inRM3BBwer9Rvcw0MSN YuM9m7YeC02F60E6eyizV0lQaz4gQKrq6BvTvL+xMHFdPABO92tYaBtpVymw9yCARB1U CLKjAqkFFn5+d9X5K7oOy+soJK/27T2zi7gqN0AA3emnS4sSKR11tjpX7pmt+2BARGdX gpb5u2jLLBYJg3b9cRrhQllLbXSUThjeEH1ASgNWuW5T9f7JKPOWMv5UWHoksJFbpJir uXDDBRofKFXn59JItWUf+JP/+0FoI9n6+8ufgYhzcxb8MzQfbKiPqGFoHalgeq38xznk u5Tw== MIME-Version: 1.0 X-Received: by 10.202.203.142 with SMTP id b136mr3065505oig.104.1444641895473; Mon, 12 Oct 2015 02:24:55 -0700 (PDT) Received: by 10.202.108.212 with HTTP; Mon, 12 Oct 2015 02:24:55 -0700 (PDT) In-Reply-To: <20FAC204-CAA3-4E36-938A-E857EE81C0A3@gmx.de> References: <20FAC204-CAA3-4E36-938A-E857EE81C0A3@gmx.de> Date: Mon, 12 Oct 2015 11:24:55 +0200 Message-ID: From: Dave Taht To: Sebastian Moeller Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: dtaht/sch_cake , cake@lists.bufferbloat.net, dtaht/sch_cake Subject: Re: [Cake] [sch_cake] Merge branch 'exposeinterval' (5541271) X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2015 09:25:19 -0000 On Mon, Oct 12, 2015 at 11:08 AM, Sebastian Moeller wrote= : > Hi Kevin, > > On Oct 12, 2015, at 10:55 , Kevin Darbyshire-Bryant wrote: > >> It's worse/better than that - if you look at cake_set_rate it actually s= ets the interval to the max of target(5ms) * 8 or the supplied interval par= ameter, so actually as it currently stands the lowest you can ACTUALLY set = interval to is 40ms. This is incorrect for the DC use case. We should be able to have the target fall below at least 250us. > Good to know, data center people might not appreciate that given = that for fq_codel a target value of 500=C2=B5sec seems to be recommended (n= ow whether fq_codel/cake really are applicable for data centers is another = question). But since I have no data center available I would not know how t= o test this, so others need to chime in. > (Note to self, it might make sense to also expose the target-para= meter, potentially not in raw time units, but as a percentage of interval, = as specified in the codel RFC draft section "4.4. The target Setpoint,=E2= =80=9D, see https://datatracker.ietf.org/doc/draft-ietf-aqm-codel/?include_= text=3D1 ). > >> >> I put those limits in purely as an anti hack/tc stupidity/pointer gone w= ild - defensive programming thing. Take 'em out/tweak/whatever. > > Oh, I am all for sanity and playing it safe, this is why I wonder= ed whether the actual limits will work for the targeted audience. It would = be sweet if the initial limits of the upstream commit could survive some ti= me, so sqm-scripts does not need any gymnastics to inform users about chang= ed behavior (so I am asking for purely selfish reasons) ;) > Loganaden, since you have experience, how long are your RTTs fro= m Mauritius to France and both US coasts (as a proxy for =E2=80=9Ctypical= =E2=80=9D traffic destinations); so we can taylor the limits to allow that. > > Best Regards > Sebastian > >> >> =E2=80=94 >> Reply to this email directly or view it on GitHub. >> > --=20 Dave T=C3=A4ht Do you want faster, better, wifi? https://www.patreon.com/dtaht