Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: dtaht/sch_cake
	<reply+005e229ba97631443eb83ca2349a0192f870114806b4dedf92cf000000011233377a92a163ce00d139a3@reply.github.com>,
	cake@lists.bufferbloat.net,
	dtaht/sch_cake <sch_cake@noreply.github.com>
Subject: Re: [Cake] [sch_cake] Merge branch 'exposeinterval' (5541271)
Date: Mon, 12 Oct 2015 11:24:55 +0200	[thread overview]
Message-ID: <CAA93jw7sLw_iREjcAxn9o6psVOEuXAtW0zTnF9D0Fp+1YhdkYw@mail.gmail.com> (raw)
In-Reply-To: <20FAC204-CAA3-4E36-938A-E857EE81C0A3@gmx.de>

On Mon, Oct 12, 2015 at 11:08 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Kevin,
>
> On Oct 12, 2015, at 10:55 , Kevin Darbyshire-Bryant <notifications@github.com> wrote:
>
>> It's worse/better than that - if you look at cake_set_rate it actually sets the interval to the max of target(5ms) * 8 or the supplied interval parameter, 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µsec seems to be recommended (now 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 to test this, so others need to chime in.
>         (Note to self, it might make sense to also expose the target-parameter, 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,”, see https://datatracker.ietf.org/doc/draft-ietf-aqm-codel/?include_text=1 ).
>
>>
>> I put those limits in purely as an anti hack/tc stupidity/pointer gone wild - defensive programming thing. Take 'em out/tweak/whatever.
>
>         Oh, I am all for sanity and playing it safe, this is why I wondered 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 time, so sqm-scripts does not need any gymnastics to inform users about changed behavior (so I am asking for purely selfish reasons) ;)
>         Loganaden, since you have experience, how long are your RTTs  from Mauritius to France and both US coasts (as a proxy for “typical” traffic destinations); so we can taylor the limits to allow that.
>
> Best Regards
>         Sebastian
>
>>
>> —
>> Reply to this email directly or view it on GitHub.
>>
>



-- 
Dave Täht
Do you want faster, better, wifi? https://www.patreon.com/dtaht

  reply	other threads:[~2015-10-12  9:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dtaht/sch_cake/commit/55412714b3d0db929c2c7d3f84d881fb6db93ca1@github.com>
     [not found] ` <dtaht/sch_cake/commit/55412714b3d0db929c2c7d3f84d881fb6db93ca1/13711779@github.com>
2015-10-12  9:08   ` Sebastian Moeller
2015-10-12  9:24     ` Dave Taht [this message]
2015-10-12  9:28       ` Jonathan Morton
2015-10-12  9:36         ` Dave Taht
2015-10-12 11:16           ` Dave Taht
2015-10-12 11:49             ` Sebastian Moeller
2015-10-12 12:04               ` Dave Taht
2015-10-12 12:06                 ` Sebastian Moeller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw7sLw_iREjcAxn9o6psVOEuXAtW0zTnF9D0Fp+1YhdkYw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=reply+005e229ba97631443eb83ca2349a0192f870114806b4dedf92cf000000011233377a92a163ce00d139a3@reply.github.com \
    --cc=sch_cake@noreply.github.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox