From: Dave Taht <dave.taht@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Codel] better mixing in fq_codel
Date: Thu, 30 Aug 2012 19:34:03 -0700 [thread overview]
Message-ID: <CAA93jw6-9+Wg+FJE4pi60NUSwkJjLyfHUVQ_NE1KWsyAavOeZg@mail.gmail.com> (raw)
In-Reply-To: <1346377256.2586.37.camel@edumazet-glaptop>
On Thu, Aug 30, 2012 at 6:40 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Thu, 2012-08-30 at 16:19 -0700, Dave Taht wrote:
>
>> In that case it will deliver 3 acks in a row from
>> stream A, and then 3 acks in stream B, in the linux 3.5 version, and
>> push the the 1500 byte packet from my example to the old flows queue -
>
> Nope, the 1500 byte packet will be sent as normal (we obviously cant
> split a packet). If its the first packet (new flow), there wont be any
> penalty.
>
>> instead of delivering A 1 ack, B 1 ack, push the C 1500 byte packet to
>> the old flows queue, then deliver A,B,A,B,A,B, A, A, A etc (and note
>> with more flows mixing gets better) as I just proposed.
>
> Try to change quantum, and it will just work out of the box.
I think, eric, that you missed this portion of the idea, and that I
mis-commented it, and worse, overstated the effect of what I was
trying to do while watching it crash...
...and seeing through the dust and clouds... off in the distance...
the desirable behavior I'd been aiming for.
...
in fq_codel_enqueue...
flow->deficit = min(q->quantum, qdisc_pkt_len(skb));
// put only 1 packet into the new flow queue unless it's more than
quantum (in which case it too will be kicked to old flows)
--
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"
prev parent reply other threads:[~2012-08-31 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 22:59 Dave Taht
2012-08-30 23:06 ` Eric Dumazet
2012-08-30 23:19 ` Dave Taht
2012-08-31 1:40 ` Eric Dumazet
2012-08-31 2:34 ` 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=CAA93jw6-9+Wg+FJE4pi60NUSwkJjLyfHUVQ_NE1KWsyAavOeZg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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