CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Anjali Chawla <anjaliachawla013@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] Setpoint in CoDel
Date: Fri, 20 Feb 2015 10:01:54 -0800	[thread overview]
Message-ID: <CAA93jw7147Ucy=fRmt-65VuUSDyVwHwH9NCmOFjq4GULYGC63A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw43TJdo9FK61HK0et3Mopq8-YKjjkNm_6_OF7+g0iMipw@mail.gmail.com>

On Fri, Feb 20, 2015 at 1:21 AM, Dave Taht <dave.taht@gmail.com> wrote:
> the best talk on the subject was van´s at ietf, it is well worth
> watching multiple times.
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos
>
> He goes deeply into the reasoning behind the sojourn time, and setpoint.
>
> About the only other somewhat in-depth talk on how codel really works
> was my attempt at stanford.

The stanford talk took some digging to find. I would really like a shot
at a do-over one day - or for van to give his talk again to be filmed at
high quality.

https://www.youtube.com/watch?v=Mxoa5Si4Ubw

>
> and there are of course other talks above that try to describe bits of
> the elephant.
>
> One of these days I hope someone puts together the definitive talk on
> codel complete with even more elegant demos than stephen hemminger
> came up with..., but it does seem to be really hard for people to get
> at a deep level... most of my own talks are more about fq than
> fq_codel, and that is *tons* easier to explain.
>
> If you watch them all a bunch of times, and run a few experiments of
> your own, enlightenment will come. For me, it was seeing kathie give
> the first public explanation of codel - about midway through I started
> vibrating in my seat - but I had just completed a slash and burn tour
> through all the aqm literature going back 30 years, and trying
> everything that seemed to make sense. I don´t know how to impart that
> in an email...
>
>
> On Fri, Feb 20, 2015 at 12:46 AM, Anjali Chawla
> <anjaliachawla013@gmail.com> wrote:
>> Hi
>> anyone please explain me what is concept behind  setpoint in codel
>> algorithm??
>> Thanks
>>
>> _______________________________________________
>> Codel mailing list
>> Codel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/codel
>>
>
>
>
> --
> Dave Täht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

      reply	other threads:[~2015-02-20 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  8:46 Anjali Chawla
2015-02-20  9:21 ` Dave Taht
2015-02-20 18:01   ` Dave Taht [this message]

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/codel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAA93jw7147Ucy=fRmt-65VuUSDyVwHwH9NCmOFjq4GULYGC63A@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=anjaliachawla013@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    /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