From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: 2.5.69 process.c: cpu_idle() cleanup
Date: Tue, 13 May 2003 06:51:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705750@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705738@msgid-missing>
>>>>> On 12 May 2003 22:09:17 -0400, Jes Sorensen <jes@wildopensource.com> said:
Jes> It was actually a deliberate decision of mine to not make it a machine
Jes> vector, because this was meant to be an optional feature. With a
Jes> machine vector one always ends up calling a dummy function on
Jes> platforms that do not wish to do anything here.
Jes> I'll be happy to change it over to a machine vector if you still
Jes> prefer, let me know.
It doesn't make a huge difference either way. But I definitely want
there to be only a single function/callback. In fact, if you load the
function pointer into a local variable, the load (and NULL check) can
be amortized across both calls and we can rest assured that we squeze
every single cycle out of the idle loop! ;-)
(Actually, on the more serious side, we don't want to waste CPU cycles
outright in the idle loop either, as that could negatively affect
power consumption---not that it makes a huge difference on current
generation CPUs.)
--david
next prev parent reply other threads:[~2003-05-13 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 23:31 [Linux-ia64] Re: 2.5.69 process.c: cpu_idle() cleanup David Mosberger
2003-05-13 0:41 ` Jes Sorensen
2003-05-13 0:48 ` David Mosberger
2003-05-13 2:09 ` Jes Sorensen
2003-05-13 6:51 ` David Mosberger [this message]
2003-05-13 18:33 ` Jes Sorensen
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=marc-linux-ia64-105590723705750@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.