From: David Miller <davem@davemloft.net>
To: tj@kernel.org
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/12]: Sparc64 dynamic per-cpu support.
Date: Wed, 08 Apr 2009 22:37:19 -0700 (PDT) [thread overview]
Message-ID: <20090408.223719.61587584.davem@davemloft.net> (raw)
This patch set converts sparc64 over to use the dynamic per-cpu stuff.
Most of the work is the boring task of getting rid of the special
"real_setup_per_cpu_areas()" sparc64 uses to setup the per-cpu areas
before bootmem is available. We needed to do this because we
initialized the cpu possible map at the same time as the stuff stored
in the per-cpu cpu_data array.
So we split those tasks up. Otherwise we wouldn't be able to convert
to dynamic per-cpu because that stuff requires that bootmem and the
page structs are ready to use.
For now I'm using the draconian unoptimized x86 NUMA remap scheme. I
really want to do this better because it is insanely suboptimal on
Niagara chips where in some cases 8 cpus share the same physical TLB.
This is against Linus's current tree and it's also in sparc-next-2.6
reply other threads:[~2009-04-09 5:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090408.223719.61587584.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®