From: Pavel Machek <pavel@ucw.cz>
To: Frantisek Rysanek <Frantisek.Rysanek@post.cz>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: Dynticks on Vortex86SX ? (Cx486SLC + just the standard i8254 PC timer)
Date: Wed, 3 Mar 2010 22:53:47 +0100 [thread overview]
Message-ID: <20100303215347.GD2579@ucw.cz> (raw)
In-Reply-To: <4B87FBC3.23033.45BDAB1@Frantisek.Rysanek.post.cz>
Hi!
> > Select HZ=100.
> >
> right
> 1) to make the numbers decadic
> 2) seems like the only true way for me to decrease the rate of PC
> timer interrupts :-)
Try HZ=20 :-).
> I am aware that the PC timer has a limited resolution (16 bits for
> the single i8254 channel) and thus the maximum time you can possibly
> sleep without an interrupt is about 55 ms (18 Hz). Based on all the
> PR publicity the dynticks patch used to receive in its time,
> I thought that even on my puny hardware, the PC timer would
> automatically flex towards that maximum period. Apparently this is
> not the case...
I guess nohz needs apic timer or something like that.
> And perhaps the hunt for dynticks is not really worth the bother,
> if the wakeup to serve IRQ0 comes once every 3 million CPU cycles :-)
> (This board clocks the CPU at 300 MHz.) How many CPU cycles does it
> take before the idle loop calls HLT again? a hundred maybe? So
> that's 1/30000 of time running out of HLT? :-)
Well, on modern cpus, entering/exiting halt state takes *lomg* time.
You are lucky.
> There's another power-saving feature of the Vortex SoC: it can
> decrease the core clock down to 1/8th of the nominal clock. This can
> be configured by a simple IO instruction. This way, you can decrease
> consumption of the whole SoC by maybe 6.5% (= down to 93% of full
> throttle), at the cost of throttling the core clock by 87%. The
> standard PC104 boards don't have a Vcore regulator, so it just
> doesn't get any better than that. I can do the underclocking from
> userspace using IOperm, I was wondering how nice it would be to have
> a "clockmod" driver, but ultimately I guess saving 125 mW is not
> worth the bother, as the whole setup including some peripherials eats
> over 3 Watts...
Yep, hooking it to cpufreq would be nice.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-03-03 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 20:45 Frantisek Rysanek
2010-02-26 11:20 ` Mikael Pettersson
2010-02-26 15:50 ` Frantisek Rysanek
2010-03-03 21:53 ` Pavel Machek [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=20100303215347.GD2579@ucw.cz \
--to=pavel@ucw.cz \
--cc=Frantisek.Rysanek@post.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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
all inboxes | Powered by JetHome®