Re: [Bloat] link saturation test failing

Re: [Bloat] link saturation test failing

[Dev]

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

Re: [Bloat] link saturation test failing

[Dave Taht]

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

Re: [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@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

[Bloat] link saturation test failing

[Dev]

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

Re: [Bloat] link saturation test failing

[Toke Høiland-Jørgensen]

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