From: Andi Kleen <ak@suse.de>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Andi Kleen <ak@suse.de>, Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] cpu-timers: high-resolution CPU clocks for POSIX clock_* syscalls
Date: Wed, 15 Dec 2004 05:51:11 +0100 [thread overview]
Message-ID: <20041215045111.GG27225@wotan.suse.de> (raw)
In-Reply-To: <a36005b50412141444432cb6c1@mail.gmail.com>
On Tue, Dec 14, 2004 at 02:44:17PM -0800, Ulrich Drepper wrote:
> On 14 Dec 2004 20:07:39 +0100, Andi Kleen <ak@suse.de> wrote:
>
> > I don't think this should be merged until a clear need from a useful
> > application is demonstrated for it.
>
> This is something which is requested countless times. Everybody doing
> development of sophisticated programs adds some kind of self
> monitoring. And there is of course profiling. The most widely used
You mean statistical profiling? I don't see why you need a bigger
resolution than HZ for that.
> program which needs this is probably the JVM. Don't ask me for the
> specific class, but the JVM developers asked for these clocks in this
> form. Without the support available the Linux JVM is never going to
They didn't ask linux-kernel at least. Perhaps their requirements
should be discussed here first before messing up all kinds of
fast paths with dubious changes?
-Andi
next prev parent reply other threads:[~2004-12-15 4:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200412140355.iBE3t7KL008040@magilla.sf.frob.com.suse.lists.linux.kernel>
2004-12-14 19:07 ` Andi Kleen
2004-12-14 22:44 ` Ulrich Drepper
2004-12-15 4:51 ` Andi Kleen [this message]
2004-12-14 3:55 Roland McGrath
2004-12-14 18:36 ` Christoph Lameter
2004-12-14 21:38 ` Ulrich Drepper
2004-12-14 21:50 ` Roland McGrath
2004-12-14 21:58 ` Christoph Lameter
2004-12-14 22:18 ` Linus Torvalds
2004-12-14 22:26 ` Ulrich Drepper
2004-12-14 22:44 ` Linus Torvalds
2004-12-14 23:08 ` Roland McGrath
2004-12-14 22:14 ` Roland McGrath
2004-12-14 22:23 ` Christoph Lameter
2004-12-15 18:43 ` Christoph Lameter
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=20041215045111.GG27225@wotan.suse.de \
--to=ak@suse.de \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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
Powered by JetHome