From: "Mario Antonio Garcia" <dino@webjogger.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Clock Source Kernel settings in 2.6.22
Date: Wed, 29 Aug 2007 13:24:10 +0000 [thread overview]
Message-ID: <45E4FD623F464B30A0067FF269007B89@shadow> (raw)
I wonder if somebody has got good results (accurate shaping) using 2.6.22?
I am testing with 2.6.22.1, and I haven't been able to get accurate shaping.
For instance, I tried:
$TC qdisc add dev eth0 root handle 1: htb default 1
$TC class add dev eth0 parent 1: classid 1:1 htb
rate 100000kbit ceil 100000kbit burst 24k cburst 24k
$TC class add dev eth0 parent 1:1 classid 1:10 htb
rate 20000kbit ceil 20000kbit burst 24k cburst 24k
and class 1:10 shapes the traffic to 19900kbit instead of 20000kbit
(bandwidth tests made with ftp and iperf)
My corresponding kernel settings are:
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_HPET_TIMER=y
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
CONFIG_HZ_1000=y
CONFIG_HZ\x1000
# CONFIG_CPU_FREQ is not set
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_FIFO=y
Notice that in 1.26.22 there are new patches for Clock Source:
http://lists.openwall.net/netdev/2007/03/16/22
"These patches convert the packet schedulers to use ktime as only clock
source and kill off the manual clock source selection. Additionally all
packet schedulers are converted to use hrtimer-based Watchdogs, greatly
increasing scheduling precision."
Regards,
Mario Antonio
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-08-29 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 13:24 Mario Antonio Garcia [this message]
2007-08-31 9:43 ` [LARTC] Clock Source Kernel settings in 2.6.22 Patrick McHardy
2007-08-31 18:46 ` Mario Antonio Garcia
2007-09-02 11:45 ` Patrick McHardy
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=45E4FD623F464B30A0067FF269007B89@shadow \
--to=dino@webjogger.net \
--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