public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Peschke <mp3@de.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, hch@infradead.org,
	arjan@infradead.org, James.Smart@Emulex.Com,
	James.Bottomley@SteelEye.com
Subject: Re: [RFC] [Patch 7/8] statistics infrastructure - exploitation prerequisite
Date: Wed, 17 May 2006 00:36:14 +0200	[thread overview]
Message-ID: <446A53DE.6060400@de.ibm.com> (raw)
In-Reply-To: <20060516112824.39b49563.akpm@osdl.org>

Andrew Morton wrote:
> Martin Peschke <mp3@de.ibm.com> wrote:
>> need sched_clock for latency statistics
> 
> sched_clock() probably isn't suitable for this application.  It's a
> scheduler thing and has a number of accuracy problems.
> 
> But I thought we discussed this last time around?  Maybe not.

I have been too obsessed with the other issues to remember.

 > Maybe you've considered sched_clock()'s drawbacks and you've decided
 > they're all acceptable.

Admittedly, I didn't, but merely believed the comment above the function.

http://marc.theaimsgroup.com/?l=linux-kernel&m=114657675408686&w=2
sheds some light.

I would be happy to exploit an API that may result from that discussion.
I would plead for exporting such an API to modules. I don't see how
to implement statistics for latencies, otherwise.

Any other hints on how to replace my sched_clock() calls are welcome.
(I want to measure elapsed times in units that are understandable to
users without hardware manuals and calculator, such as milliseconds.)

Martin


  reply	other threads:[~2006-05-16 22:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 17:47 [RFC] [Patch 7/8] statistics infrastructure - exploitation prerequisite Martin Peschke
2006-05-16 18:28 ` Andrew Morton
2006-05-16 22:36   ` Martin Peschke [this message]
2006-05-16 23:03     ` Arnd Bergmann
2006-05-17  1:23       ` Peter Chubb
2006-05-17  1:27         ` Andi Kleen
2006-05-17  1:43           ` Peter Chubb
2006-05-17  2:24             ` Christoph Lameter
2006-05-17  1:13     ` Peter Chubb
2006-05-17  2:32   ` Nick Piggin

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=446A53DE.6060400@de.ibm.com \
    --to=mp3@de.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=James.Smart@Emulex.Com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=hch@infradead.org \
    --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