All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com, ak@suse.de
Subject: Re: per_cpu fixes
Date: Thu, 10 Jul 2003 11:37:31 +0200	[thread overview]
Message-ID: <20030710093731.GC17798@wotan.suse.de> (raw)
In-Reply-To: <20030710015208.1E7A22C44B@lists.samba.org>

> When I implemented this, I imagined archs putting their per-cpu offset
> inside a register, so they could get to their vars in one instruction,
> but not the IA64 remapping thing.  We are now suffering because of my
> limited imagination (which David has commented on before 8).

x86-64 has similar problems. While the virtual addresses are different
the direct access using the segment register doesn't yield an address
(there is no LEA instruction to read from segment registers). It can be
worked around, but you have to follow an indirect pointer.
For most efficient access you can't take the address.

[currently the code doesn't use the Segment access for per_cpu data,
but I plan to readd this eventually]

-Andi

  reply	other threads:[~2003-07-10  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 21:20 per_cpu fixes David Mosberger
2003-07-09 21:56 ` David Mosberger
2003-07-10  1:41 ` Rusty Russell
2003-07-10  9:37   ` Andi Kleen [this message]
2003-07-10 17:55   ` David Mosberger
2003-07-10 18:15     ` Linus Torvalds
2003-07-10 18:22       ` David Mosberger
2003-07-11  2:01     ` Rusty Russell
2003-07-11  2:08       ` David Mosberger

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=20030710093731.GC17798@wotan.suse.de \
    --to=ak@suse.de \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@transmeta.com \
    /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.