From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Martin Peschke <mp3@de.ibm.com>,
linux-kernel@vger.kernel.org, ak@suse.de, hch@infradead.org,
arjan@infradead.org, James.Smart@Emulex.Com,
James.Bottomley@SteelEye.com, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC] [Patch 7/8] statistics infrastructure - exploitation prerequisite
Date: Wed, 17 May 2006 12:32:40 +1000 [thread overview]
Message-ID: <446A8B48.5060107@yahoo.com.au> (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.
>
>Maybe you've considered sched_clock()'s drawbacks and you've decided
>they're all acceptable. If so, the changelog should have described the
>reasoning.
>
Yeah; please, no more users of sched_clock(). Definitely don't export.
Even if it is what you want today (which it probably isn't), the scheduler
might want the ability to change it at short notice, depending on new
algorithms / new hardware etc. in future.
Make a new function if none of the suggested alternatives work.
--
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2006-05-17 2:32 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
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 [this message]
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=446A8B48.5060107@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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 \
--cc=mingo@elte.hu \
--cc=mp3@de.ibm.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