From: Greg White <g.white@CableLabs.com>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] head drop vs tail drop
Date: Fri, 15 Oct 2021 17:09:03 +0000 [thread overview]
Message-ID: <DCB678A0-D908-420B-8247-4587EE6145C0@cablelabs.com> (raw)
In-Reply-To: <CAA93jw6H8UmbgQ0O-oL8sCCJXz_DSq-4YHmsGjNa6QaJNU8i0w@mail.gmail.com>
Be careful with the terminology, since there are two types of head drop:
1) head drop based on sojourn time
2) head drop based on current queue depth
That paper used type 2.
In type 1, the drop is based on the queue that existed at the time "this" packet was enqueued (i.e. the packets that arrived *before* this packet), and thus is equivalent* to tail drop. In type 2, the drop is based on the queue caused by the packets that arrive *after* this packet.
* modulo the difference in predicted queue delay vs measured queue delay.
Type 2 detects and signals congestion more quickly than tail drop. Type 1 is the same as tail drop.
-Greg
On 10/10/21, 12:32 PM, "Bloat on behalf of Dave Taht" <bloat-bounces@lists.bufferbloat.net on behalf of dave.taht@gmail.com> wrote:
We've never really characterized the differences between head and tail
drop. A good tidbit went
by here, where in one experiment 15 v 22 drops were observed.
https://journal.ub.tu-berlin.de/eceasst/article/view/1137/1092
Last paper I'm forwarding for the day!
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2021-10-15 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 18:32 Dave Taht
2021-10-15 17:09 ` Greg White [this message]
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=DCB678A0-D908-420B-8247-4587EE6145C0@cablelabs.com \
--to=g.white@cablelabs.com \
--cc=bloat@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