From: Martin Krejcirik <mk@krej.cz>
To: lartc@vger.kernel.org
Subject: [LARTC] SFQ
Date: Wed, 26 Nov 2003 15:02:32 +0000 [thread overview]
Message-ID: <marc-lartc-106985920913627@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100814354131080@msgid-missing>
Hi,
could anybody enlighten me how SFQ is supposed to work, please ?
Consider this simple script:
tc qdisc add dev eth0 root handle 1: htb default 1 r2q 10
tc class add dev eth0 parent 1:0 classid 1:1 htb rate 1Mbit ceil 1Mbit
tc qdisc add dev eth0 parent 1:1 sfq perturb 120
#tc qdisc add dev eth0 parent 1:1 pfifo limit 100
tc filter add dev eth0 parent 1:0 protocol ip prio 200 u32 \
match ip dst 192.168.1.1 flowid 1:1
tc filter add dev eth0 parent 1:0 protocol ip prio 200 u32 \
match ip dst 192.168.1.2 flowid 1:1
A single class limited to 1Mbit, sfq or pfifo attached to it and two
filters.
I try to send some traffic from localhost to above two IPs, but I see
absolutely no difference, whether I use sfq or pfifo qdisc. I thought
when I send say 1.2Mbit UDP to 192.168.1.1, then ping to 192.168.1.2
should be low (go through the other queue), but this is not happening.
Or when I send 5Mbit/s to one IP and then try ftp to the other, I get
almost nothing through, I thought this was that was SFQ supposed to prevent ?
Could anybody describe some scenario, where I can see difference between
sfq and fifo, please ?
thanks,
bye
__________________________________________________
Martin Krejcirik <mk@krej.cz>, PGP KeyID: B030351D
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-11-26 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 7:50 [LARTC] SFQ Don Cohen
2001-12-12 9:31 ` bert hubert
2003-11-26 15:02 ` Martin Krejcirik [this message]
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=marc-lartc-106985920913627@msgid-missing \
--to=mk@krej.cz \
--cc=lartc@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