From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dev <dev@logicalwebhost.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] link saturation test failing
Date: Mon, 31 Dec 2018 21:39:40 +0100 [thread overview]
Message-ID: <875zv9fn1v.fsf@toke.dk> (raw)
In-Reply-To: <E59212A6-5401-413A-90FB-890DF79D3AEC@logicalwebhost.com>
Dev <dev@logicalwebhost.com> writes:
> I’m running Debian Buster, trying to saturate a link, enable fq_codel
> and drop my ping times back down, but they seem to stay high.
>
> I connected machine A and B to a gig switch, then dropped the port
> speed on machine A like:
>
> ethtool -s enp8s0 advertise 0x002
From which machine are you running the test? If your bottleneck is the
switch, that is where the buffering will happen; FQ-CoDel on the host
can do nothing about that...
-Toke
next prev parent reply other threads:[~2018-12-31 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 17:29 Dev
2018-12-31 20:39 ` Toke Høiland-Jørgensen [this message]
2019-01-03 17:16 Dev
2019-01-03 17:18 ` Dave Taht
2019-01-03 21:17 ` Dev
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=875zv9fn1v.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=dev@logicalwebhost.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