From: Paul Mackerras <paulus@samba.org>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pmac_cpufreq msleep cleanup/fixes
Date: Sat, 23 Oct 2004 10:33:59 +1000 [thread overview]
Message-ID: <16761.42743.34328.919506@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20041022234344.GI18906@us.ibm.com>
Nishanth Aravamudan writes:
> Looks good to me... And makes quite a bit of sense, after I thought
> about it. Does feel a little hacky, but I don't see a slicker way around
> the problem...
We would need a platform-specific function to tell us how long until
the next jiffy to do any better, I think, and even then it would only
make much of a difference if HZ was significantly smaller than 1000.
We could do the how-long-until-next-jiffy function quite easily and
quickly on ppc and ppc64, just by reading the decrementer register and
scaling it. I don't know about other architectures. But if we are
mostly using HZ=1000 there doesn't seem to be much point.
Paul.
next prev parent reply other threads:[~2004-10-23 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410221906.i9MJ63Ai022889@hera.kernel.org>
2004-10-22 22:36 ` Benjamin Herrenschmidt
2004-10-22 22:53 ` Linus Torvalds
2004-10-22 23:17 ` Benjamin Herrenschmidt
2004-10-22 23:43 ` Nishanth Aravamudan
2004-10-23 0:33 ` Paul Mackerras [this message]
2004-10-22 23:51 ` Linus Torvalds
2004-10-25 0:19 ` [PATCH][RESEND] Fix msleep to sleep _at_least_ the requested amount Benjamin Herrenschmidt
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=16761.42743.34328.919506@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®