From: Eric Dumazet <eric.dumazet@gmail.com>
To: Karel Rericha <karel@maxtel.cz>
Cc: netdev@vger.kernel.org
Subject: Re: Quick Fair Queue scheduler maturity and examples
Date: Thu, 27 Oct 2011 18:27:12 +0200 [thread overview]
Message-ID: <1319732832.2601.43.camel@edumazet-laptop> (raw)
In-Reply-To: <1319731732.2601.40.camel@edumazet-laptop>
Le jeudi 27 octobre 2011 à 18:08 +0200, Eric Dumazet a écrit :
> Le jeudi 27 octobre 2011 à 14:46 +0200, Karel Rericha a écrit :
>
> > Actually I am doing some reseach to replace our main shaping machine
> > with 60 000+ htb classes, which now saturates 12 core Xeon Westmere to
> > 30% (there are five gigabit network ports on each interface affinited
> > to cores). AFAIK QFQ should be O(1) complexity so it would bring
> > saturation a requirements for number of cores down considerably (HTB
> > has O(log(N)) complexity).
> >
> > I have test machine and about two months to decide if we will stay
> > with HTB or we will try something else. So it would be VERY helpful,
> > if you would search you memory instead your dead disk :-) and send me
> > some example of QFQ usage, if I can ask for a little of your time. I
> > promise to have results published here in return.
> >
> > Thanks, Karel
> >
>
> That seems a good challenge to me ;)
>
> First upgrade to a recent kernel with QFQ included.
> Also upgrade iproute2 to a recent enough version as well.
>
> Then you discover "tc ... qfq help" is not that helpful :(
>
> # tc qdisc add dev eth3 root qfq help
> Usage: ... qfq
>
> OK, its parameters are :
>
> qfq weight num1 [maxpkt BYTES]
>
> You should not touch maxpkt, its default value being 2048
>
> Oh well, I just tried the obvious and my (remote) machine doesnt answer
> to me anymore...
>
> Time for a bit of debugging I am afraid :(
Never mind, it was an user error :)
Here is what I used during my tests, I guess you can adapt your
scripts...
DEV=eth3
RATE="rate 40Mbit"
TNETS="10.2.2.0/25"
ALLOT="allot 20000"
tc qdisc del dev dummy0 root 2>/dev/null
tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 rate 1000Mbit \
bandwidth 1000Mbit
tc class add dev $DEV parent 1: classid 1:1 \
est 1sec 8sec cbq allot 10000 mpu 64 \
rate 1000Mbit prio 1 avpkt 1500 bounded
# output to test nets : 40 Mbit limit
tc class add dev $DEV parent 1:1 classid 1:11 \
est 1sec 8sec cbq $ALLOT mpu 64 \
$RATE prio 2 avpkt 1400 bounded
tc qdisc add dev $DEV parent 1:11 handle 11: \
est 1sec 8sec qfq
tc filter add dev $DEV protocol ip parent 11: handle 3 \
flow hash keys rxhash divisor 8
for i in `seq 1 8`
do
classid=11:$(printf %x $i)
tc class add dev $DEV classid $classid qfq
tc qdisc add dev $DEV parent $classid pfifo limit 30
done
for privnet in $TNETS
do
tc filter add dev $DEV parent 1: protocol ip prio 100 u32 \
match ip dst $privnet flowid 1:11
done
tc filter add dev $DEV parent 1: protocol ip prio 100 u32 \
match ip protocol 0 0x00 flowid 1:1
iperf -u -c 10.2.2.1 -P 32 -l 50
next prev parent reply other threads:[~2011-10-27 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 11:30 Quick Fair Queue scheduler maturity and examples Karel Rericha
2011-10-27 11:59 ` Eric Dumazet
2011-10-27 12:46 ` Karel Rericha
2011-10-27 16:08 ` Eric Dumazet
2011-10-27 16:27 ` Eric Dumazet [this message]
2011-11-02 9:36 ` Karel Rericha
2011-11-02 10:05 ` David Täht
[not found] ` <4EB115F7.5070203-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-02 10:31 ` Eric Dumazet
2011-11-02 11:31 ` David Täht
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=1319732832.2601.43.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=karel@maxtel.cz \
--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