From: Dev <dev@logicalwebhost.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] link saturation test failing
Date: Thu, 27 Dec 2018 09:29:38 -0800 [thread overview]
Message-ID: <E59212A6-5401-413A-90FB-890DF79D3AEC@logicalwebhost.com> (raw)
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
Then verified the link lights on switch show 10M. Then try to enable fq_codel and swamp link like:
tc qdisc add dev enp8s0 root fq_codel
dd if=/dev/urandom | ssh user@192.168.10.150 dd of=/dev/null
I still have high ping times (10msec vs 0.5 msec). I try to saturate with iperf and the same thing happens. Then I try to look at fq_codel like:
tc qdisc show dev enp8s0
qdisc fq_codel 8001: root refcnt 6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
and
tc -g -s class show dev enp8s0
+---(:5) mq
| Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
| backlog 0b 0p requeues 0
|
+---(:4) mq
| Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
| backlog 0b 0p requeues 0
|
+---(:3) mq
| Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
| backlog 0b 0p requeues 0
|
+---(:2) mq
| Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
| backlog 0b 0p requeues 0
|
+---(:1) mq
Sent 248411320 bytes 164594 pkt (dropped 0, overlimits 0 requeues 4)
backlog 0b 0p requeues 4
But I don’t really know what I should be looking for/doing.
-Dev
next reply other threads:[~2018-12-27 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 17:29 Dev [this message]
2018-12-31 20:39 ` Toke Høiland-Jørgensen
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=E59212A6-5401-413A-90FB-890DF79D3AEC@logicalwebhost.com \
--to=dev@logicalwebhost.com \
--cc=bloat@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