From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, "Dave Täht" <dave.taht@bufferbloat.net>
Subject: Re: [Codel] [RFC PATCH] Codel: Enable packet drop with ECN-marked packets on a threshold
Date: Mon, 18 Jun 2012 05:10:30 +0200 [thread overview]
Message-ID: <1339989030.7491.328.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw5X3BHfC_Yv=QCn+6sRf66UppLHaDbNOKEZoX-e1-QKsw@mail.gmail.com>
On Sun, 2012-06-17 at 22:40 -0400, Dave Taht wrote:
> (side note, I noticed fq_codel defaulted to 10k packets which is
> rather excessive for tiny routers - I just trimmed that down
> significantly for cerowrt and the upcoming 3.3.8-4 release has the rfc
> patch in it)
>
> And apologies for not seeing this long ago,
10k packets is too small to absorb a burst of 64bytes packets on 10Gb
links. Whole CoDel point is to accept packets at enqueue and drop them
at dequeue _if_ sejourn time too big. Number of packets should be
irrelevant.
If you don't know how much packet can be sent on wire per unit of time,
just set a reasonable big limit.
1000 packets limit is not reasonable, while 10k is.
linux average machines have more ram than tiny routers, dont assume we
release specialized code. It should be generic enough, granted it can be
easily tuned.
next prev parent reply other threads:[~2012-06-18 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 22:30 Dave Täht
2012-06-18 2:17 ` Eric Dumazet
2012-06-18 2:40 ` Dave Taht
2012-06-18 2:58 ` Eric Dumazet
2012-06-18 3:01 ` Dave Taht
2012-06-18 3:10 ` Eric Dumazet [this message]
2012-06-18 3:21 ` Dave Taht
2012-06-18 3:50 ` 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=1339989030.7491.328.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@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