From: davidsen@tmr.com (bill davidsen)
To: rml@tech9.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] I3 sched tweaks...
Date: Thu, 17 Jan 2002 08:01:50 -0500 [thread overview]
Message-ID: <200201171301.IAA01133@gatekeeper.tmr.com> (raw)
In-Reply-To: <1011216429.1083.95.camel@phantasy>
In-Reply-To: <1011215946.314.14.camel@gs256.sp.cs.cmu.edu>
In article <1011216429.1083.95.camel@phantasy> you write:
| On Wed, 2002-01-16 at 16:19, Justin Carlson wrote:
|
| > Don't forget that, in non-x86 land, current tends to be just kept in a
| > register. No computations required. Certainly passing it around on,
| > e.g. mips is a clear loss.
|
| current is stored in a register (esp) in x86, too. This is why I
| cautioned that looking up current was cheap -- I think every sane arch
| stores current in some fast access way. That's why it is a macro -- it
| is assembly code to quickly snag the address.
|
| So is passing current still worth it?
It sounds as if it may be one of those "it depends" things, but if
current is not calculated the exact same way in all places... people
talk about coloring (or colouring in Canada) and several other things I
forget, it's sort of nice to be sure it's calculated just once, and that
if the calculation becomes more expensive in the future that the
tradeoff between passing and calculating won't change.
I guess passing is safer for the future and of a known cost.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2002-01-17 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 5:49 [PATCH] I3 sched tweaks Rusty Russell
2002-01-16 9:15 ` Ingo Molnar
2002-01-16 9:17 ` Ingo Molnar
2002-01-16 10:34 ` Rusty Russell
2002-01-16 22:46 ` Ingo Molnar
2002-01-16 21:10 ` Robert Love
2002-01-16 21:19 ` Justin Carlson
2002-01-16 21:27 ` Robert Love
2002-01-16 23:31 ` Ingo Molnar
2002-01-17 13:01 ` bill davidsen [this message]
2002-01-16 21:31 ` Paul Mackerras
2002-01-17 3:37 ` Rusty Russell
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=200201171301.IAA01133@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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