From: "Sven Köhler" <skoehler@upb.de>
To: linux-kernel@vger.kernel.org
Subject: alternatives to getrusage() ?
Date: Wed, 06 Sep 2006 23:56:42 +0200 [thread overview]
Message-ID: <edng6u$kcc$1@sea.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
Hi,
first, if this is the wrong place to ask, then i'm sorry and please
recomm a better place to me.
My goal is to do some precise benchmarking/profiling.
I am looking for (Linux specific) alternatives to getrusage().
As far as i understand, the precision of getrusage() is given by the
timer frequency that can be adjusted in recent kernel-versions. I think
i have the choice between 100Hz, 250Hz and 1000Hz. By chosing 1000Hz, i
get a precision of 1ms, right?
On the other hand, there are things like rdtsc() which reads the clock
counter of the CPU. So does the linux kernel currently provide a
process-specific value which counts the CPU clocks "consumed" by a
process? Maybe there are some patches?
Are there other alternatives that i didn't think about yet?
Are there maybe some kernel-unrelated alternatives?
Thanks,
Sven
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
reply other threads:[~2006-09-06 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='edng6u$kcc$1@sea.gmane.org' \
--to=skoehler@upb.de \
--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 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.