From: Thomas Gleixner <tglx@linutronix.de>
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: RE: [PATCH] provide hrtimer exports for module use [Was: Exports for hrtimer APIs]
Date: Tue, 14 Mar 2006 23:18:14 +0100 [thread overview]
Message-ID: <1142374694.19916.663.camel@localhost.localdomain> (raw)
In-Reply-To: <CBDB88BFD06F7F408399DBCF8776B3DC06A92BAC@scsmsx403.amr.corp.intel.com>
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
next prev parent reply other threads:[~2006-03-14 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 22:11 Stone, Joshua I
2006-03-14 22:18 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 21:01 Stone, Joshua I
2006-03-14 21:36 ` Andrew Morton
2006-03-14 22:03 ` Christoph Hellwig
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=1142374694.19916.663.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=joshua.i.stone@intel.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
all inboxes | Powered by JetHome®