From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] some 110Mbit cable testing of the new dslreports stuff
Date: Tue, 28 Apr 2015 01:58:31 +0300 [thread overview]
Message-ID: <CAJq5cE18t8oaqV8XDi9EayoR5w=pRJ2f7Wbg8jw_ikLvftLSrw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6-vRfGPHMMs17bXbYaqL1+5oA0fp5L=w9Pf5UsynHLRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
Well, shaping downstream of the true bottleneck is somewhat less effective
than shaping upstream of it. Transiently, some of the queue is in the link
FIFO rather than in the managed queue.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 247 bytes --]
next prev parent reply other threads:[~2015-04-27 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 21:28 Dave Taht
2015-04-27 22:56 ` Dave Taht
2015-04-28 6:59 ` jb
2015-04-27 22:58 ` Jonathan Morton [this message]
2015-04-30 4:47 ` Dave Taht
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='CAJq5cE18t8oaqV8XDi9EayoR5w=pRJ2f7Wbg8jw_ikLvftLSrw@mail.gmail.com' \
--to=chromatix99@gmail.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