From: Chuck Ebbert <76306.1226@compuserve.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
Jan Beulich <jbeulich@novell.com>,
Zachary Amsden <zach@vmware.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH RFC 0/6] Implement per-processor data areas for i386.
Date: Wed, 30 Aug 2006 05:00:33 -0400 [thread overview]
Message-ID: <200608300503_MC3-1-C9C4-92F7@compuserve.com> (raw)
In-Reply-To: <20060827084417.918992193@goop.org>
On Sun, 27 Aug 2006 01:44:17 -0700, Jeremy Fitzhardinge wrote:
> This patch implements per-processor data areas by using %gs as the
> base segment of the per-processor memory.
This changes the ABI for signals and ptrace() and that seems like
a bad idea to me.
And the way things are done now is so ingrained into the i386
kernel that I'm not sure it can be done. E.g. I found two
open-coded implementations of current, one in kernel_fpu_begin()
and one in math_state_restore().
> - It also allows per-CPU data to be allocated as each CPU is brought
> up, rather than statically allocating it based on the maximum number
> of CPUs which could be brought up.
Can you describe what it is about the way things work now that
prevents dynamic allocation?
--
Chuck
next reply other threads:[~2006-08-30 9:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 9:00 Chuck Ebbert [this message]
2006-08-30 9:17 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2006-08-30 12:33 Chuck Ebbert
2006-08-30 12:54 ` Andi Kleen
2006-08-30 16:39 ` Jeremy Fitzhardinge
2006-08-30 16:48 ` Andi Kleen
2006-08-30 17:13 ` Jeremy Fitzhardinge
2006-08-30 17:32 ` Andi Kleen
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=200608300503_MC3-1-C9C4-92F7@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome