General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: jb <justin@dslr.net>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
	bloat <Bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports bufferbloat tests
Date: Thu, 21 Apr 2016 05:22:51 +0300	[thread overview]
Message-ID: <B6D9B396-8ABF-4985-8B36-25FC8680D764@gmail.com> (raw)
In-Reply-To: <CAH3Ss97wHA8qGvxFf6=L0MpxrB15QuxHdsQ75LfQdn+A6BfWAA@mail.gmail.com>


> On 21 Apr, 2016, at 01:53, jb <justin@dslr.net> wrote:
> 
> So Is there anything different, or detectable, on the server side for
> such a fully congestion aware connection, but no congestion is
> encountered?

This would imply that your server was unable to saturate the connection.  You should be able to infer this case by comparing the measured throughput to your server’s capacity.

> So on upload phase, I can see CE marks come in, but during download
> phase there is nothing interesting to detect and log?

Since the router handling the queue for the bottleneck link will likely be different in each direction (in the simple case, one is at the ISP and the other is in the subscriber’s home), it’s entirely possible for one direction to be fully ECN-aware and AQMed at the bottleneck, and the other to be completely bloated.  In both cases, the traffic will negotiate ECN (or not) the same way.

Additionally, even if there are ECN-aware, AQMed queues on the path, it’s the bottleneck queue that counts.  It’s possible to get some sporadic CE marks on a path where the major bottleneck link is bloated, if the traffic passes through an ECN-aware pinch point which is transiently congested.

 - Jonathan Morton


  reply	other threads:[~2016-04-21  2:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  1:04 Dave Taht
2016-04-06  1:33 ` Brandon Applegate
2016-04-06  2:21   ` Dave Taht
2016-04-06  3:19     ` jb
2016-04-06 15:30       ` Dave Taht
2016-04-06 16:08         ` Kelvin Edmison
2016-04-07 18:13           ` Livingood, Jason
2016-04-07 18:23             ` Livingood, Jason
2016-04-20  6:06             ` jb
2016-04-20  6:10               ` Dave Taht
2016-04-20 12:43               ` Jonathan Morton
2016-04-20 22:53                 ` jb
2016-04-21  2:22                   ` Jonathan Morton [this message]
2016-04-07  2:06         ` jb
2016-04-07  2:14           ` Jonathan Morton
2016-04-07 18:16         ` Livingood, Jason

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=B6D9B396-8ABF-4985-8B36-25FC8680D764@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=Bloat@lists.bufferbloat.net \
    --cc=Jason_Livingood@comcast.com \
    --cc=justin@dslr.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