CoDel AQM discussions
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] Exploring the potential of codel, fq_codel, and qfq
Date: Wed, 16 May 2012 09:46:57 +0200	[thread overview]
Message-ID: <1337154417.8512.1147.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw5Yb+wSb0vCBrH6x+ED87z4qWi6t1OdZ6ws4KQhbOn25Q@mail.gmail.com>

On Wed, 2012-05-16 at 00:20 -0700, Dave Taht wrote:

> With ecn:
> 
> 64 bytes from 149.20.63.18: icmp_req=46 ttl=64 time=10.6 ms
> 64 bytes from 149.20.63.18: icmp_req=47 ttl=64 time=5.66 ms
> 64 bytes from 149.20.63.18: icmp_req=48 ttl=64 time=11.8 ms
> 64 bytes from 149.20.63.18: icmp_req=49 ttl=64 time=3.68 ms
> 64 bytes from 149.20.63.18: icmp_req=50 ttl=64 time=10.2 ms
> 64 bytes from 149.20.63.18: icmp_req=51 ttl=64 time=12.8 ms
> 64 bytes from 149.20.63.18: icmp_req=52 ttl=64 time=2.62 ms
> 64 bytes from 149.20.63.18: icmp_req=53 ttl=64 time=7.86 ms
> 
> TCP_RR: 102
> 
> All of these sets of results need more rigor attached.

On TCP_RR pure workload, you have one packet in flight per flow.

ECN adds nothing in this case, only that no 'drops' occurs at all.

It might be good to change fq_codel to perform ECN mark only if flow
queue has more packets.

If not, plain drop.




  parent reply	other threads:[~2012-05-16  7:47 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09  1:04 [Codel] The challenge Dave Taht
2012-05-09  2:02 ` [Codel] [Bloat] " Kevin Gross
2012-05-09  3:13 ` [Codel] " Kathleen Nichols
2012-05-09  3:56   ` Dave Taht
2012-05-09  5:16 ` [Codel] [Bloat] " Simon Barber
2012-05-09  5:40   ` Eric Dumazet
2012-05-09  5:41     ` Dave Taht
2012-05-09  7:32       ` [Codel] [codel] some numbers on dual 10Gb links Eric Dumazet
2012-05-09 13:04   ` [Codel] [Bloat] The challenge Kevin Gross
2012-05-16  5:55     ` Jonathan Morton
2012-05-16  6:09       ` Eric Dumazet
2012-05-16  7:05         ` [Codel] Exploring the potential of codel, fq_codel, and qfq dave taht
2012-05-16  7:20           ` Dave Taht
2012-05-16  7:42             ` [Codel] [Bloat] " Eric Dumazet
2012-05-16  7:46             ` Eric Dumazet [this message]
2012-05-16  8:17               ` Eric Dumazet
2012-05-16  9:02                 ` Jonathan Morton
2012-05-16  9:14                   ` Eric Dumazet
2012-05-16  9:31                     ` Jonathan Morton
2012-05-16  9:37                       ` Eric Dumazet
2012-05-16  9:59                         ` Jonathan Morton
2012-05-16 10:10                           ` Eric Dumazet
2012-05-16 13:58                 ` Eric Dumazet
2012-05-16 17:40               ` Rick Jones
2012-05-16 17:53                 ` Eric Dumazet
2012-05-16 17:33             ` [Codel] " Rick Jones
2012-05-16 17:48               ` [Codel] [Bloat] " Eric Dumazet
2012-05-16  6:09       ` [Codel] [Bloat] The challenge Dave Taht
2012-05-16  6:31         ` Eric Dumazet
2012-05-16  8:15           ` Jonathan Morton
2012-05-09 19:10   ` Roger Jørgensen
2012-05-09 19:15     ` Dave Taht
2012-05-09 19:28       ` Dave Taht
2012-05-09 20:02     ` Simon Barber
2012-05-09 20:06   ` Fred Baker
2012-05-09 21:47     ` Jim Gettys
2012-05-09 23:58       ` Eric Dumazet
2012-05-10  2:34 ` Jonathan Morton
2012-05-10  2:37   ` Dave Taht
2012-05-10  6:35     ` David Woodhouse
2012-05-10  6:54       ` Jonathan Morton
2012-05-10  7:02         ` David Woodhouse
2012-05-10 14:25           ` Justin McCann
2012-05-10 14:42             ` David Woodhouse
2012-05-10 15:34               ` Neil Davies
2012-05-10 21:20               ` Jim Gettys
2012-05-14  7:27           ` Jonathan Morton
2012-05-14  7:34             ` Eric Dumazet
2012-05-14 13:55             ` David Woodhouse
2012-05-18 20:56               ` [Codel] [Bloat] Linux-able modems Jonathan Morton
2012-05-18 21:36                 ` Dave Taht
2012-05-18 22:34                   ` Dave Taht

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=1337154417.8512.1147.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@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