From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel M/L <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Final glitch1 report WRT cfs
Date: Sat, 21 Jul 2007 17:30:15 -0400 [thread overview]
Message-ID: <46A27AE7.9050706@tmr.com> (raw)
At least on my hardware, the cfs in 2.6.22-git13 runs as smoothly as the
perfect smoothness of cfs-v13, with two tuning changes:
sched_stat_granularity_ns = 1000000
sched_features = 14
The change in "features" made a major improvement.
Having identified the cause of the better smoothness in the older
version, I'm going to put my efforts into other characterizations. The
test source will remain on the server, but I'm won't do more with it
unless someone finds it useful.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
reply other threads:[~2007-07-21 21:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46A27AE7.9050706@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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