public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Justin Carlson <justincarlson@cmu.edu>
Cc: mingo@elte.hu, Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] I3 sched tweaks...
Date: 16 Jan 2002 16:27:09 -0500	[thread overview]
Message-ID: <1011216429.1083.95.camel@phantasy> (raw)
In-Reply-To: <1011215946.314.14.camel@gs256.sp.cs.cmu.edu>
In-Reply-To: <Pine.LNX.4.33.0201162343290.18971-100000@localhost.localdomain>  <1011215440.814.82.camel@phantasy>  <1011215946.314.14.camel@gs256.sp.cs.cmu.edu>

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?

	Robert Love


  reply	other threads:[~2002-01-16 21:26 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 [this message]
2002-01-16 23:31             ` Ingo Molnar
2002-01-17 13:01           ` bill davidsen
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=1011216429.1083.95.camel@phantasy \
    --to=rml@tech9.net \
    --cc=justincarlson@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    /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