From: Matthew Wilcox <willy@debian.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] sched_clock implementation
Date: Thu, 18 Sep 2003 21:35:10 +0100 [thread overview]
Message-ID: <20030918203510.GD21596@parcelfarce.linux.theplanet.co.uk> (raw)
Anyone want to do better than the lame implementation? ;-)
----- Forwarded message from Andrew Morton <akpm@osdl.org> -----
I'll be merging Ingo & Con's CPOU scheduler changes into Linus's tree soon.
It does require that the architecture provides a new timing function:
A lame implementation is:
/*
* Returns nanoseconds
*/
unsigned long long sched_clock(void)
{
return (unsigned long long)jiffies * (1000000000 / HZ);
}
But for best CPU scheduler results the architecture should try to return a
higher-resolution number than this of course.
sched_clock() has no absolute time requirements: it just has to return some
number which goes up by 1,000,000,000 times per second.
I already have implementations for x86, ppc, sparc64 and ia64.
I have a completely stupid ppc64 implementation which is only accurate on
1GHz CPUs. Anton please note!
As for the rest, it'll break the build, sorry.
----- End forwarded message -----
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next reply other threads:[~2003-09-18 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 20:35 Matthew Wilcox [this message]
2003-09-19 15:32 ` [parisc-linux] sched_clock implementation Joel Soete
2003-09-19 16:00 ` Carlos O'Donell
2003-09-19 16:11 ` Joel Soete
2003-09-20 18:02 ` Joel Soete
2003-09-21 0:04 ` Grant Grundler
2003-09-21 11:20 ` Helge Deller
2003-09-21 14:24 ` Carlos O'Donell
2003-10-05 15:43 ` Joel Soete
2003-10-06 14:20 ` Carlos O'Donell
[not found] ` <3F5CB6FB0000DCF3@ocpmta1.freegates.net>
2003-10-06 17:31 ` Carlos O'Donell
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=20030918203510.GD21596@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=parisc-linux@parisc-linux.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