Subject: RE: [PATCH] provide hrtimer exports for module use [Was: Exports
	for hrtimer APIs]
From: Thomas Gleixner <tglx@linutronix.de>
Reply-To: tglx@linutronix.de
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
In-Reply-To: <CBDB88BFD06F7F408399DBCF8776B3DC06A92BAC@scsmsx403.amr.corp.intel.com>
References: <CBDB88BFD06F7F408399DBCF8776B3DC06A92BAC@scsmsx403.amr.corp.intel.com>
Content-Type: text/plain
Date: Tue, 14 Mar 2006 23:18:14 +0100
Message-Id: <1142374694.19916.663.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1052
Lines: 23

On Tue, 2006-03-14 at 14:11 -0800, Stone, Joshua I wrote:
> Sure - SystemTap uses timers to provide an asynchronous probe during
> module execution.  This might be utilized for polling kernel states, for
> flushing trace data, and perhaps other similar uses.  Currently we're
> using the main timer APIs - add_timer, mod_timer, etc.
> 
> My motivation for moving to hrtimer is because of what I read in its
> documentation - basically that the timer wheel is best for timeout cases
> which are rarely recascaded.  The way SystemTap uses timers is more for
> defining intervals, and they are always cascaded until the module is
> complete.  The hrtimers seem more suited to this methodology.

What means "more for defining intervals" ? Which intervals  (period in
ms)? What are the timers used for ?

	tglx


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/