From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Zachary Amsden <zach@vmware.com>,
Jan Beulich <jbeulich@novell.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH RFC 0/6] Implement per-processor data areas for i386.
Date: Wed, 30 Aug 2006 18:48:39 +0200 [thread overview]
Message-ID: <200608301848.39443.ak@suse.de> (raw)
In-Reply-To: <44F5BF29.7080004@goop.org>
>
> I don't think so. The whole point is to make the pda easily accessible
> with simple addressing modes based on %gs:. I have been wondering if
> we can modify the percpu mechanism to get the linker to construct the
> layout of the pda, so that all the existing percpu stuff can be
> transparently moved into the pda and accessed efficiently. I think it
> would be pretty tricky to get it all working though...
I tried that once on x86-64, but it wasn't possible because the linker
is missing the right relocations. It has something on the first look similar
for __thread data in user space, but it wasn't usable for the kernel.
Even with a single indirection it is still far more efficient than a
array lookup.
-Andi
next prev parent reply other threads:[~2006-08-30 16:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 12:33 [PATCH RFC 0/6] Implement per-processor data areas for i386 Chuck Ebbert
2006-08-30 12:54 ` Andi Kleen
2006-08-30 16:39 ` Jeremy Fitzhardinge
2006-08-30 16:48 ` Andi Kleen [this message]
2006-08-30 17:13 ` Jeremy Fitzhardinge
2006-08-30 17:32 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-08-30 9:00 Chuck Ebbert
2006-08-30 9:17 ` Jeremy Fitzhardinge
2006-08-28 9:06 Chuck Ebbert
2006-08-27 8:44 Jeremy Fitzhardinge
2006-08-27 9:47 ` Arjan van de Ven
2006-08-27 16:46 ` Jeremy Fitzhardinge
2006-08-27 17:44 ` Arjan van de Ven
2006-08-27 18:07 ` Andi Kleen
2006-08-27 18:27 ` Jeremy Fitzhardinge
2006-08-27 16:01 ` Andi Kleen
2006-08-27 16:41 ` Jeremy Fitzhardinge
2006-08-27 17:21 ` Andreas Mohr
2006-08-27 17:34 ` Jeremy Fitzhardinge
2006-08-27 18:23 ` Andreas Mohr
2006-08-27 18:04 ` Andi Kleen
2006-08-27 18:27 ` Andreas Mohr
2006-08-27 18:35 ` Andi Kleen
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=200608301848.39443.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.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.