From: Eric Dumazet <eric.dumazet@gmail.com>
To: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
Cc: netdev@vger.kernel.org
Subject: Re: SFQ on HFSC leaf does not seem to work
Date: Fri, 23 Dec 2011 15:00:22 +0100 [thread overview]
Message-ID: <1324648822.2223.18.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <1324647920.2223.14.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
Le vendredi 23 décembre 2011 à 14:45 +0100, Eric Dumazet a écrit :
> 1) What kernel version do you use ?
>
> 2) How many concurrent flows are running (number of netperf/netcat)
>
> 3) Remind that 'perturb xxx' introduces a temporary doubling of the
> number of flows.
>
> 4) Had you disabled tso on eth1 ?
> (If not, you might send 64Kbytes packets, and at 400kbit, they take a
> lot of time to transmit : more than one second ...)
>
>
Using your script on net-next, (only using eth3 instead of eth1) and
ethtool -K eth3 tso off
ethtool -K eth3 gso off
ip ro flush cache
one ssh : dd if=/dev/zero | ssh 192.168.0.1 "dd of=/dev/null"
my ping is quite good :
$ ping -c 20 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
2011/11/23 14:57:01.106 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=59.4 ms
2011/11/23 14:57:02.121 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=72.7 ms
2011/11/23 14:57:03.109 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=60.3 ms
2011/11/23 14:57:04.108 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=57.8 ms
2011/11/23 14:57:05.115 64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=62.6 ms
2011/11/23 14:57:06.116 64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=62.6 ms
2011/11/23 14:57:07.112 64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=57.6 ms
2011/11/23 14:57:08.127 64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=70.9 ms
2011/11/23 14:57:09.123 64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=65.4 ms
2011/11/23 14:57:10.113 64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=53.5 ms
2011/11/23 14:57:11.127 64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=66.7 ms
2011/11/23 14:57:12.129 64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=67.4 ms
2011/11/23 14:57:13.119 64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=56.3 ms
2011/11/23 14:57:14.127 64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=64.0 ms
2011/11/23 14:57:15.116 64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=51.9 ms
2011/11/23 14:57:16.127 64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=61.2 ms
2011/11/23 14:57:17.127 64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=60.4 ms
2011/11/23 14:57:18.135 64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=68.2 ms
2011/11/23 14:57:19.137 64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=69.1 ms
2011/11/23 14:57:20.136 64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=67.0 ms
--- 192.168.0.1 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19022ms
rtt min/avg/max/mdev = 51.909/62.796/72.751/5.579 ms
$ tc -s -d class show dev eth3
class hfsc 1: root
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
period 0 level 2
class hfsc 1:1 parent 1: sc m1 0bit d 0us m2 1490Kbit ul m1 0bit d 0us m2 1490Kbit
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
period 69 work 38559740 bytes level 1
class hfsc 1:10 parent 1:1 leaf 1101: rt m1 327680bit d 50.0ms m2 200000bit ls m1 0bit d 0us m2 1000Kbit
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
period 0 level 0
class hfsc 1:20 parent 1:1 leaf 1201: rt m1 0bit d 0us m2 400000bit ls m1 0bit d 0us m2 200000bit
Sent 38587058 bytes 27022 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 19p requeues 0
period 69 work 38559740 bytes rtwork 10358780 bytes level 0
class hfsc 1:30 parent 1:1 leaf 1301: rt m1 605600bit d 20.0ms m2 20000bit
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
period 0 level 0
class sfq 1201:f7 parent 1201:
(dropped 0, overlimits 0 requeues 0)
backlog 25804b 18p requeues 0
allot -1336
Hmm... we probably could fill hfsc class information with non null bytes backlog...
I'll take a look.
next prev parent reply other threads:[~2011-12-23 14:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 6:00 SFQ on HFSC leaf does not seem to work John A. Sullivan III
2011-12-23 6:32 ` Dave Taht
2011-12-23 6:40 ` John A. Sullivan III
2011-12-23 7:08 ` John A. Sullivan III
2011-12-23 8:10 ` Eric Dumazet
2011-12-23 13:13 ` John A. Sullivan III
2011-12-23 13:45 ` Eric Dumazet
2011-12-23 14:00 ` Eric Dumazet [this message]
2011-12-23 14:38 ` John A. Sullivan III
2011-12-23 14:59 ` Eric Dumazet
2011-12-23 15:26 ` John A. Sullivan III
2011-12-23 16:16 ` Eric Dumazet
2011-12-23 16:44 ` John A. Sullivan III
2011-12-23 17:06 ` Eric Dumazet
2011-12-23 17:17 ` Eric Dumazet
2011-12-23 17:33 ` John A. Sullivan III
2011-12-23 17:35 ` John A. Sullivan III
2011-12-23 21:10 ` John A. Sullivan III
2011-12-23 22:24 ` Eric Dumazet
2011-12-23 17:20 ` John A. Sullivan III
2011-12-31 22:17 ` John A. Sullivan III
2011-12-23 15:19 ` [PATCH net-next] sch_hfsc: report backlog information Eric Dumazet
2011-12-23 21:52 ` David Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1324648822.2223.18.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=jsullivan@opensourcedevel.com \
--cc=netdev@vger.kernel.org \
/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