From: Pavel Machek <pavel@ucw.cz>
To: george@mvista.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: VST patches ported to 2.6.11-rc1
Date: Fri, 14 Jan 2005 01:11:18 +0100 [thread overview]
Message-ID: <20050114001118.GA1367@elf.ucw.cz> (raw)
In-Reply-To: <20050113132641.GA4380@elf.ucw.cz>
Hi!
> I really hate sf download system... Here are those patches (only
> common+i386) ported to 2.6.11-rc1.
Good news is it booted. But I could not measure any powersavings by
turning it on. (I could measure difference between HZ=100 and
HZ=1000).
Hmm, it does not want to do anything. threshold used to be 1000, does
it mean that it would not use vst unless there was one second of quiet
state? I tried to lower it to 10 ("get me HZ=100 power consumption")
but it does not seem to be used, anyway:
root@amd:/proc/sys/kernel/vst# cat successful_vst_exit
0
root@amd:/proc/sys/kernel/vst# cat external_intr_exit
0
root@amd:/proc/sys/kernel/vst#
> +config HIGH_RES_RESOLUTION
> + int "High Resolution Timer resolution (nanoseconds)"
> + depends on HIGH_RES_TIMERS
> + default 1000
> + help
> + This sets the resolution in nanoseconds of the CLOCK_REALTIME_HR and
> + CLOCK_MONOTONIC_HR timers. Too fine a resolution (small a number)
> + will usually not be observable due to normal system latencies. For an
> + 800 MHz processor about 10,000 (10 microseconds) is recommended as a
> + finest resolution. If you don't need that sort of resolution,
> + larger values may generate less overhead.
Ugh, if minimum recomended value is 10K, why does it have 1K as a
default?
> + The system boots with VST enabled and it can be disabled by:
> + "echo 0 > /proc/sys/kernel/vst/enable".
It definitely booted with vst disabled here... echo 1 did the trick
through.
>short_timer_fns This is an array of 5 entries of the form
> ...
> 0xc110ea80 when the timer expires.
>Both of these arrays are kept as circular lists and read back such
>that
>the latest entry is presented to the reader first. The entries are
>cleared when read.
...it is bad idea to have them world-readable, then.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-01-14 0:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 13:26 Pavel Machek
2005-01-13 19:23 ` George Anzinger
2005-01-13 20:02 ` Pavel Machek
2005-01-13 21:20 ` Tony Lindgren
2005-01-14 0:11 ` Pavel Machek [this message]
2005-01-14 1:03 ` George Anzinger
2005-01-19 23:14 ` George Anzinger
2005-01-19 23:32 ` Tony Lindgren
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=20050114001118.GA1367@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=george@mvista.com \
--cc=linux-kernel@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
Powered by JetHome