From: John Reiser <jreiser@BitWagon.com>
To: peter@mysql.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Measuring per thread CPU consumption & others statistics for NPTL
Date: Mon, 17 Nov 2003 08:36:32 -0800 [thread overview]
Message-ID: <3FB8F910.6080000@BitWagon.com> (raw)
In-Reply-To: <SNSi.6vN.39@gated-at.bofh.it>
Peter Zaitsev wrote:
> On Mon, 2003-11-17 at 03:27, Peter Chubb wrote:
>>If you apply my microstate accounting patch, you can get nanosecomnd
>>resolution per thread.
>
> Is it planned to be included in the kernel at some point ?
> For me it is the most important not to get things working on some
> particular test systems, but to allow customers, which run generic or
> vendor provided kernels to use the functionality.
The current 2.6.0-test9-bk22 has no microsecond-or-finer per-thread
accounting, so based on current policy and past experience you may
have to wait two years.
A leading contender for x86 and x86_64 is the perfctr patches
http://www.csd.uu.se/~mikpe/linux/perfctr/ which have been maintained
for a number of years (v1.0 at 2000-01-31 for Linux 2.2.14/2.3.41) and
have a following, including http://icl.cs.utk.edu/projects/papi/ .
A recent patched, ready-to-install NPTL kernel happens to reside at
http://www.BitWagon.com/ftp/kernel-smp-2.4.20-20.9.perfctr2.5.5.i686.rpm .
For a complete profiler: http://www.BitWagon.com/tsprof/tsprof.html
which also will run on a generic kernel in "-wallclock" mode
(TSC cycle accuracy, but not virtualized.)
--
next parent reply other threads:[~2003-11-17 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SxNf.4R.13@gated-at.bofh.it>
[not found] ` <SFro.3ee.13@gated-at.bofh.it>
[not found] ` <SNSi.6vN.39@gated-at.bofh.it>
2003-11-17 16:36 ` John Reiser [this message]
2003-11-16 16:10 Measuring per thread CPU consumption & others statistics for NPTL Peter Zaitsev
2003-11-17 0:27 ` Peter Chubb
2003-11-17 9:25 ` Peter Zaitsev
2003-11-20 18:02 ` Herbert Poetzl
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=3FB8F910.6080000@BitWagon.com \
--to=jreiser@bitwagon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@mysql.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.