public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: "'high-res-timers-discourse@lists.sourceforge.net'" 
	<high-res-timers-discourse@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] VST (tick elimination) is now available
Date: Fri, 10 Oct 2003 15:19:19 -0700	[thread overview]
Message-ID: <3F873067.9020805@mvista.com> (raw)

The first release of the VST package is now available.  VST or 
Variable Scheduling Timeouts (or if you prefer, Variable Sleep Times) 
contains code that, from the idle task, scans the timer list and, if 
no timer is near, skips the timer interrupts that would otherwise be 
generated.  The patch name is hrtimers-vst-*

The net result is that a quite system will use far less power as it 
does not need to wake up ever 1/HZ timer tick.

This patch depends on the high-res-timers patch version
hrtimers-2.4.20-3.0 which must be applied first.

Both of these patchs are on sourceforge at:

http://sourceforge.net/projects/high-res-timers/

Some details:

There is a proc directory (/proc/sys/kernel/vst/) dedicated to vst 
controls.  Root may turn VST on or off here with "echo "0">enable. 
There is also a log option (danger Will Robinson) which, if turned on 
causes " x" where x is the number of ticks being skipped, to be 
printed on the log console.  This will quickly swamp the console, but 
it does show things happening during quite times and no such output 
when the system is busy.  It is also possible to set the threshold 
here.  This is in units of milliseconds and is the time the next timer 
must away from now to trigger a VST sleep.  Currently this is set 
rather large considering that we can sleep only 50ms, but you can 
change it here.

The file .../include/linux/vst.h contains details on the arch 
interface.  The core code is all in .../kernel/timer.c with enabling 
bits in various places.  The arch code for the x86 version is all 
located in .../include/asm-i386/hrtime.h

This is, of course, the first cut at this stuff.  There is a lot left 
to do....

Things left to do:

Currently the PIT is used to wake the system for the next timer.  If 
that timer is further away than about 50ms, the PITs limitations force 
us to use the max PIT time of about 50ms.  We plan to use the rtc 
hardware to do this wake up, thus eliminating this restriction.

SMP imposes further restrictions and, as it currently stands, may 
cause late timers in some cases.  When we port to the 2.6 kernel this 
will change, for the better, we hope :)  This will also allow us to 
use the APIC timers in these systems to do the wake up, thus allowing 
longer sleep times.
-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


             reply	other threads:[~2003-10-10 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 22:19 George Anzinger [this message]
2003-10-14 11:02 ` [ANNOUNCE] VST (tick elimination) is now available Pavel Machek
2003-10-14 12:41   ` George Anzinger

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=3F873067.9020805@mvista.com \
    --to=george@mvista.com \
    --cc=high-res-timers-discourse@lists.sourceforge.net \
    --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