Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Welzl <michawe@ifi.uio.no>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat]  DOCSIS 3+ recommendation?
Date: Fri, 20 Mar 2015 14:54:07 +0000	[thread overview]
Message-ID: <CA35CD7C-A717-4DCE-ADE6-0B81E1DCAB97@ifi.uio.no> (raw)
In-Reply-To: <D131A022.FD6D9%jason_livingood@cable.comcast.com>

Folks,

I think I have just seen this statement a little too often:

> That’s right, Jim. The “some packet loss is good” part is from what I have seen the hardest thing for people to understand. People have been trained to believe that any packet loss is terrible (..)

I understand the "wrong mindset" thing and the idea of AQM doing something better. Still, I'd like people to understand that packet loss often also comes with delay - for having to retransmit. This delay is not visible in the queue, but it's visible in the end system. It also comes with head-of-line blocking delay on the receiver side: at least with TCP, whatever has been received after a dropped packet needs to wait in the OS for the hole to be filled before it can be handed over to the application.

Here we're not talking a few ms more or less in the queue, we're talking an RTT, when enough DupACKs are produced to make the sender clock out the missing packet again. Else, we're talking an RTO, which can be much, much more than an RTT, and which is what TLP tries to fix (but TLP's timer is also 2 RTTs - so this is all about delay at RTT-and-higher magnitudes).

Again, significant delay can come from dropped packets - you just don't see it when all you measure is the queue. ECN can help.

Cheers,
Michael


  reply	other threads:[~2015-03-20 14:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 20:35 [Cerowrt-devel] " Matt Taggart
2015-03-17 23:32 ` Valdis.Kletnieks
2015-03-18  4:34   ` David P. Reed
2015-03-18  6:26     ` Jonathan Morton
2015-03-18 19:38       ` JF Tremblay
2015-03-18 19:50         ` Jonathan Morton
2015-03-19 13:53           ` dpreed
2015-03-19 14:11             ` JF Tremblay
2015-03-19 15:38               ` dpreed
2015-03-19 15:40               ` Jim Gettys
2015-03-19 17:04                 ` Michael Richardson
2015-03-19 17:14                   ` Jonathan Morton
2015-03-19 17:11             ` Dave Taht
2015-03-19 19:58               ` [Cerowrt-devel] [Bloat] " Livingood, Jason
2015-03-19 20:29                 ` dpreed
2015-03-19 23:18                   ` Greg White
2015-03-20  8:18                     ` MUSCARIELLO Luca IMT/OLN
2015-03-20 13:31                       ` David P. Reed
2015-03-20 13:46                         ` Sebastian Moeller
2015-03-20 14:05                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 10:07                     ` Sebastian Moeller
2015-03-20 13:50                     ` [Cerowrt-devel] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) Rich Brown
2015-03-29 17:36                       ` [Cerowrt-devel] [Bloat] " Pedro Tumusok
2015-03-30  7:06                         ` Jonathan Morton
2015-03-20 13:57                     ` [Cerowrt-devel] [Bloat] DOCSIS 3+ recommendation? Livingood, Jason
2015-03-20 14:08                       ` David P. Reed
2015-03-20 14:14                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 14:48                           ` Matt Mathis
2015-03-20 18:04                         ` Valdis.Kletnieks
2015-03-20 13:48                 ` Jim Gettys
2015-03-20 14:11                   ` Livingood, Jason
2015-03-20 14:54                     ` Michael Welzl [this message]
2015-03-20 15:31                       ` Jim Gettys
2015-03-20 15:39                         ` Michael Welzl
2015-03-20 16:31                       ` Jonathan Morton
2015-03-20 20:59                         ` Michael Welzl
2015-03-20 23:47                           ` David P. Reed
2015-03-21  0:08                             ` Michael Welzl
2015-03-21  0:03                           ` David Lang
2015-03-21  0:13                             ` Steinar H. Gunderson
2015-03-21  0:25                               ` David Lang
2015-03-21  0:34                                 ` Jonathan Morton
2015-03-21  0:38                                   ` David Lang
2015-03-21  0:43                                     ` Jonathan Morton
2015-03-22  4:15                                 ` Michael Welzl
2015-03-21  0:15                             ` Michael Welzl
2015-03-21  0:29                               ` David Lang
2015-03-22  4:10                                 ` Michael Welzl
2015-03-20 18:14                     ` Jonathan Morton
2015-03-18  8:06     ` [Cerowrt-devel] " Sebastian Moeller

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA35CD7C-A717-4DCE-ADE6-0B81E1DCAB97@ifi.uio.no \
    --to=michawe@ifi.uio.no \
    --cc=Jason_Livingood@cable.comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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