From: Dev <dev@logicalwebhost.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] link saturation test failing
Date: Thu, 3 Jan 2019 13:17:17 -0800 [thread overview]
Message-ID: <30445889-0357-4BFE-BF88-2848C7C8A50F@logicalwebhost.com> (raw)
In-Reply-To: <CAA93jw5veGNH=BFFxyEODHVfdmgbjg0j6hdxKoY4+8=WOgjrzQ@mail.gmail.com>
#>: cd /sys/class/net/eth0/queues/tx-0/byte_queue_limits
/sys/class/net/eth0/queues/tx-0/byte_queue_limits >: ls
hold_time inflight limit limit_max limit_min
/sys/class/net/eth0/queues/tx-0/byte_queue_limits >: cat limit
250
- Dev
> On Jan 3, 2019, at 9:18 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> My guess is your ethernet device does not have BQL. To check, cd
> /sys/class/net/your_device/queues/tx-0/byte_queue_limits and see if
> you have a limit other than 0.
>
> On Thu, Jan 3, 2019 at 9:16 AM Dev <dev@logicalwebhost.com> wrote:
>>
>> 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
>>
>> I’m running the test from machine A, my Debian Buster server, so that’s the interface I’ve set to 10Mbps. Basically trying to follow the howto on the website, but my ping times aren’t dropping once fq_codel is enabled.
>>
>> -Dev
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740
next prev parent reply other threads:[~2019-01-03 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 17:16 Dev
2019-01-03 17:18 ` Dave Taht
2019-01-03 21:17 ` Dev [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-27 17:29 Dev
2018-12-31 20:39 ` Toke Høiland-Jørgensen
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=30445889-0357-4BFE-BF88-2848C7C8A50F@logicalwebhost.com \
--to=dev@logicalwebhost.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