From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Nandita Dukkipati <nanditad@google.com>,
netdev <netdev@vger.kernel.org>,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
Tomas Hruby <thruby@google.com>
Subject: Re: [Codel] [RFC v2] fq_codel : interval servo on hosts
Date: Tue, 04 Sep 2012 17:39:09 +0200 [thread overview]
Message-ID: <1346773149.13121.44.camel@edumazet-glaptop> (raw)
In-Reply-To: <1C18E243-42BC-46F0-A336-EAD9BC881C45@gmail.com>
On Tue, 2012-09-04 at 18:25 +0300, Jonathan Morton wrote:
> I think that in most cases, a long RTT flow and a short RTT flow on
> the same interface means that the long RTT flow isn't bottlenecked
> here, and therefore won't ever build up a significant queue - and that
> means you would want to track over the shorter interval. Is that a
> reasonable assumption?
>
This would be reasonable, but if we have a shorter interval, this means
we could drop packets of the long RTT flow sooner than expected.
Thats because the drop_next value is setup on the previous packet, and
not based on the 'next packet'
Re-evaluating drop_next at the right time would need more cpu cycles.
next prev parent reply other threads:[~2012-09-04 15:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 6:55 [Codel] fq_codel : interval servo Eric Dumazet
2012-08-31 13:41 ` Jim Gettys
2012-08-31 13:50 ` [Codel] [RFC] fq_codel : interval servo on hosts Eric Dumazet
2012-08-31 13:57 ` [Codel] [RFC v2] " Eric Dumazet
2012-09-01 1:37 ` Yuchung Cheng
2012-09-01 12:51 ` Eric Dumazet
2012-09-04 15:10 ` Nandita Dukkipati
2012-09-04 15:25 ` Jonathan Morton
2012-09-04 15:39 ` Eric Dumazet [this message]
2012-09-04 15:34 ` Eric Dumazet
2012-09-04 16:40 ` Dave Taht
2012-09-04 16:54 ` Eric Dumazet
2012-09-04 16:57 ` Eric Dumazet
2012-08-31 15:53 ` [Codel] fq_codel : interval servo Rick Jones
2012-08-31 16:23 ` Eric Dumazet
2012-08-31 16:59 ` Dave Taht
2012-09-01 12:53 ` Eric Dumazet
2012-09-02 18:08 ` Dave Taht
2012-09-02 18:17 ` Dave Taht
2012-09-02 23:28 ` Eric Dumazet
2012-09-02 23:23 ` Eric Dumazet
2012-09-03 0:18 ` Dave Taht
2012-08-31 16:40 ` Jim Gettys
2012-08-31 16:49 ` Jonathan Morton
2012-08-31 17:15 ` Jim Gettys
2012-08-31 17:31 ` Rick Jones
2012-08-31 17:44 ` Jim Gettys
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=1346773149.13121.44.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=nanditad@google.com \
--cc=netdev@vger.kernel.org \
--cc=thruby@google.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