This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: Measuring system call times, elapsed and cpu

From: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
To: "Mike Mason" <mmlnx at us dot ibm dot com>
Cc: <systemtap at sourceware dot org>
Date: Wed, 19 Sep 2007 10:19:39 -0700
Subject: RE: Measuring system call times, elapsed and cpu
References: <46F05029.7040705@us.ibm.com> <16D5B9AB904B0B46B22A27002EE3A8C8EACABF@scsmsx415.amr.corp.intel.com> <46F13F20.8070500@us.ibm.com>

Mike Mason wrote:
> Now that I think about it some more, utime and stime aren't fine
> grained enough.  They're only updated every timer tick.  Is there
> some other way to measure real cpu time between function entry and
> exit?

CFS offers better precision through task_utime() and task_stime(), but
those don't appear to be exported.

Josh

References:
- Measuring system call times, elapsed and cpu
  - From: Mike Mason
- RE: Measuring system call times, elapsed and cpu
  - From: Stone, Joshua I
- Re: Measuring system call times, elapsed and cpu
  - From: Mike Mason

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]