From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
netdev@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Time in Queue, bufferbloat, and... our accidentally interplanetary network
Date: Wed, 07 Dec 2011 11:15:38 +0100 [thread overview]
Message-ID: <9dfc3c5eb811f2774b378fce0158b3e7@localhost> (raw)
In-Reply-To: <1323082774.2670.40.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
On Mon, 05 Dec 2011 11:59:34 +0100, Eric Dumazet wrote:
> Adding a time limit is possible, all we need is a proper design and
> implementation :)
>
> Here is my suggestion :
>
> Design a new tfifo/tred qdisc, with following properties :
>
> Adaptative RED, (ECN enabled + head drop), but instead of using
> bytes/packet qlen average, use time_in_queue average.
Question one: is anything wrong with sfb or choke as the basis, instead of
RED?
Question two: I submitted pfast_head_drop to drop more outdated data
instead of new data. Back in time I thought TCP _may_ experience benefits
because more up-to-date SACK data packets are saved. Are there any other
TCP advantages with head drop policy?
Hagen
next prev parent reply other threads:[~2011-12-07 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 9:05 Dave Taht
2011-12-05 10:59 ` Eric Dumazet
2011-12-06 2:03 ` Adrian Chadd
2011-12-07 9:59 ` Dave Taht
2011-12-07 10:15 ` Hagen Paul Pfeifer [this message]
2011-12-07 10:19 ` Hagen Paul Pfeifer
2011-12-07 11:53 ` Eric Dumazet
2011-12-08 16:06 ` [Bloat] [PATCH net-next] sch_red: Adaptative RED AQM Eric Dumazet
2011-12-08 17:21 ` Stephen Hemminger
2011-12-08 18:16 ` Eric Dumazet
2011-12-09 0:55 ` David Miller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9dfc3c5eb811f2774b378fce0158b3e7@localhost \
--to=hagen@jauu.net \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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