From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
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:19:29 +0100 [thread overview]
Message-ID: <11877422e38eade300dd1cdb9e423d47@localhost> (raw)
In-Reply-To: <9dfc3c5eb811f2774b378fce0158b3e7@localhost>
On Wed, 07 Dec 2011 11:15:38 +0100, Hagen Paul Pfeifer <hagen@jauu.net>
wrote:
> 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?
Small comment: pfast_head_drop was intended for UDP. E.g. OLSR messages,
regular GPS reporting and the like. TCP was not the focus at that time.
HGN
WARNING: multiple messages have this Message-ID (diff)
From: Hagen Paul Pfeifer <hagen-GvnIQ6b/HdU@public.gmane.org>
To: Hagen Paul Pfeifer <hagen-GvnIQ6b/HdU@public.gmane.org>
Cc: linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bloat-devel
<bloat-devel-JXvr2/1DY2fm6VMwtOF2vx4hnT+Y9+D1@public.gmane.org>,
bloat <bloat-JXvr2/1DY2fm6VMwtOF2vx4hnT+Y9+D1@public.gmane.org>
Subject: Re: Time in Queue, bufferbloat, and... our accidentally interplanetary network
Date: Wed, 07 Dec 2011 11:19:29 +0100 [thread overview]
Message-ID: <11877422e38eade300dd1cdb9e423d47@localhost> (raw)
In-Reply-To: <9dfc3c5eb811f2774b378fce0158b3e7@localhost>
On Wed, 07 Dec 2011 11:15:38 +0100, Hagen Paul Pfeifer <hagen-GvnIQ6b/HdU@public.gmane.org>
wrote:
> 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?
Small comment: pfast_head_drop was intended for UDP. E.g. OLSR messages,
regular GPS reporting and the like. TCP was not the focus at that time.
HGN
next prev parent reply other threads:[~2011-12-07 10:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 9:05 Time in Queue, bufferbloat, and... our accidentally interplanetary network Dave Taht
2011-12-05 9:05 ` Dave Taht
2011-12-05 10:59 ` Eric Dumazet
2011-12-06 2:03 ` Adrian Chadd
2011-12-06 2:03 ` Adrian Chadd
2011-12-07 9:59 ` Dave Taht
2011-12-07 9:59 ` Dave Taht
2011-12-07 10:15 ` [Bloat] " Hagen Paul Pfeifer
2011-12-07 10:15 ` Hagen Paul Pfeifer
2011-12-07 10:19 ` Hagen Paul Pfeifer [this message]
2011-12-07 10:19 ` Hagen Paul Pfeifer
2011-12-07 11:53 ` [Bloat] " Eric Dumazet
2011-12-08 16:06 ` [PATCH net-next] sch_red: Adaptative RED AQM Eric Dumazet
2011-12-08 16:06 ` Eric Dumazet
2011-12-08 17:21 ` Stephen Hemminger
2011-12-08 17:21 ` Stephen Hemminger
2011-12-08 18:16 ` Eric Dumazet
2011-12-09 12:46 ` [PATCH net-next] sch_red: generalize accurate MAX_P support to RED/GRED/CHOKE Eric Dumazet
2011-12-09 18:46 ` David Miller
2011-12-09 0:55 ` [PATCH net-next] sch_red: Adaptative RED AQM 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11877422e38eade300dd1cdb9e423d47@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.