CoDel AQM discussions
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Eric Dumazet <eric.dumazet@gmail.com>,
	 "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] Fwd: Re: "Controlling Queue Delay" article...
Date: Tue, 08 May 2012 10:47:07 -0400	[thread overview]
Message-ID: <4FA931EB.8050001@freedesktop.org> (raw)
In-Reply-To: <1336487895.3752.2413.camel@edumazet-glaptop>

On 05/08/2012 10:38 AM, Eric Dumazet wrote:
Let's try to keep things on list...
                - Jim

> On Mon, 2012-05-07 at 20:06 -0700, Kathleen Nichols wrote:
>> Okay, some more tweaks or fixes. I'm finally going through code slowly
>> and also
>> traces from sims. This fix makes it act more like the code I used to do
>> all those
>> sims. mea culpa, but hey, you guys pushed us, so caveat emptor.
>>
>> in dodqueue:
>>
>> dodeque_result codel_queue_t::dodeque(time_t now)
>> {
>>       dodeque_result r = { 0, queue::deque() };
>>       if (r.p == NULL) {
>>             first_above_time = 0;
>>       } else {
>>             time_t sojourn_time = now - r.p->tstamp;
>>             if (sojourn_time < target) {
>>                   // went below so we'll stay below for at least interval
>>                   first_above_time = 0;
>>             } else {
>>                   if (first_above_time == 0) {
>>                         // just went above from below. if we stay above
>>                         // for at least interval we'll say it's ok to drop
>>                         first_above_time = now + interval;
>>                   } else if (now >= first_above_time && bytes() >=
>> maxpacket) {
>>                         r.ok_to_drop = 1;
>>                   }
>>             }
>>       }
>>       return r;
>> }
>
> Ack, I will change our code to match this.
>
> Thanks
>
>


           reply	other threads:[~2012-05-08 14:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1336487895.3752.2413.camel@edumazet-glaptop>]

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=4FA931EB.8050001@freedesktop.org \
    --to=jg@freedesktop.org \
    --cc=codel@lists.bufferbloat.net \
    --cc=eric.dumazet@gmail.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