mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Frantisek Rysanek" <Frantisek.Rysanek@post.cz>
To: linux-kernel@vger.kernel.org
Subject: Dynticks on Vortex86SX ? (Cx486SLC + just the standard i8254 PC timer)
Date: Thu, 25 Feb 2010 21:45:41 +0100	[thread overview]
Message-ID: <4B86EF85.12688.440738@Frantisek.Rysanek.post.cz> (raw)

Dear Gentlemen,

I'm having fun with a Vortex-based motherboard, under 2.6.33.
Linux reports the CPU as a Cx486SLC :-)
A complete PC-compatible motherboard (without VGA) running at ~ 2 
Watts.
I'm wondering how to decrease the power consumption even further,
and "tickless" operation comes to mind.
And that's where I have a problem. Even if I enable 
"Tickless System (Dynamic Ticks)" in the menuconfig,
there's no apparent change in consumption, and I still get 
around 200-300 timer interrupts per second...

These are some entries from my .config that might be relevant:

CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_M486=y
CONFIG_HZ_250=y
CONFIG_HZ=250

The only timer that this platform contains (known to Linux)
is the generic i8254-compatible PC timer.

Makes me wonder if this platform is capable of "tickless" operation
at all. Or maybe my particular combination of features in the .config
effectively prevents the long idle periods from occurring?

Apart from a standard init and getty's, there's a dhclient and sshd 
running on the machine... it's a fairly minimal text-mode system.

Any ideas are welcome :-)

Frank Rysanek


             reply	other threads:[~2010-02-25 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 20:45 Frantisek Rysanek [this message]
2010-02-26 11:20 ` Mikael Pettersson
2010-02-26 15:50   ` Frantisek Rysanek
2010-03-03 21:53     ` Pavel Machek

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=4B86EF85.12688.440738@Frantisek.Rysanek.post.cz \
    --to=frantisek.rysanek@post.cz \
    --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

all inboxes | Powered by JetHome®