From: "Jerry Jongerius" <jerryj@duckware.com>
To: "'David Lang'" <david@lang.hm>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] The Dark Problem with AQM in the Internet?
Date: Fri, 29 Aug 2014 10:37:10 -0400 [thread overview]
Message-ID: <002a01cfc396$ba5c8510$2f158f30$@duckware.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1408281857550.23856@nftneq.ynat.uz>
> did you check to see if packets were re-sent even if they weren't lost? on
of
> the side effects of excessive buffering is that it's possible for a packet
to
> be held in the buffer long enough that the sender thinks that it's been
> lost and retransmits it, so the packet is effectivly 'lost' even if it
actually
> arrives at it's destination.
Yes. A duplicate packet for the missing packet is not seen.
The receiver 'misses' a packet; starts sending out tons of dup acks (for all
packets in flight and queued up due to bufferbloat), and then way later, the
packet does come in (after the RTT caused by bufferbloat; indicating it is
the 'resent' packet).
next prev parent reply other threads:[~2014-08-29 14:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 18:16 Jerry Jongerius
2014-08-23 19:30 ` Jonathan Morton
2014-08-23 20:01 ` Sebastian Moeller
2014-08-25 17:13 ` Greg White
2014-08-25 18:09 ` Jim Gettys
2014-08-25 19:12 ` Sebastian Moeller
2014-08-25 21:17 ` Bill Ver Steeg (versteb)
2014-08-25 21:20 ` Bill Ver Steeg (versteb)
2014-08-28 13:19 ` Jerry Jongerius
2014-08-28 14:07 ` Jonathan Morton
2014-08-28 17:20 ` Jerry Jongerius
2014-08-28 17:41 ` Dave Taht
2014-08-28 18:15 ` Jonathan Morton
2014-08-29 14:21 ` Jerry Jongerius
2014-08-29 16:31 ` Jonathan Morton
2014-08-29 16:54 ` Jerry Jongerius
2014-08-28 18:59 ` Sebastian Moeller
2014-08-29 11:33 ` Jerry Jongerius
2014-08-29 12:18 ` Sebastian Moeller
2014-08-29 14:42 ` Dave Taht
2014-08-29 1:59 ` David Lang
2014-08-29 14:37 ` Jerry Jongerius [this message]
2014-08-30 6:05 ` Jonathan Morton
2014-08-30 6:28 ` Stephen Hemminger
2014-08-30 6:45 ` Jonathan Morton
2014-09-01 17:30 ` Jerry Jongerius
2014-09-01 17:40 ` Dave Taht
2014-08-28 14:39 ` Rich Brown
2014-08-28 16:20 ` Jerry Jongerius
2014-08-28 16:35 ` Fred Baker (fred)
2014-08-28 18:00 ` Jan Ceuleers
2014-08-28 18:13 ` Dave Taht
2014-08-29 1:57 ` David Lang
2014-08-28 18:41 ` Kenyon Ralph
2014-08-28 19:04 ` Dave Taht
2014-08-28 16:36 ` Greg White
2014-08-28 16:52 ` Bill Ver Steeg (versteb)
2014-09-01 11:47 ` Richard Scheffenegger
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='002a01cfc396$ba5c8510$2f158f30$@duckware.com' \
--to=jerryj@duckware.com \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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