[Bloat] link saturation test failing

[Dev]

#>: 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 at 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 at logicalwebhost.com> wrote:
>> 
>> Dev <dev at 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 at lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
> 
> 
> 
> -- 
> 
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740