From: Andi Kleen <ak@suse.de>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: travis@sgi.com, Andi Kleen <ak@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 0/6] x86: Reduce Memory Usage and Inter-Node message traffic (v2)
Date: Sat, 25 Aug 2007 11:24:35 +0200 [thread overview]
Message-ID: <20070825092434.GE16227@bingen.suse.de> (raw)
In-Reply-To: <20070825005017.GC1894@linux-os.sc.intel.com>
On Fri, Aug 24, 2007 at 05:50:18PM -0700, Siddha, Suresh B wrote:
> On Fri, Aug 24, 2007 at 03:26:54PM -0700, travis@sgi.com wrote:
> > Previous Intro:
>
> Thanks for doing this.
>
> > In x86_64 and i386 architectures most arrays that are sized
> > using NR_CPUS lay in local memory on node 0. Not only will most
> > (99%?) of the systems not use all the slots in these arrays,
> > particularly when NR_CPUS is increased to accommodate future
> > very high cpu count systems, but a number of cache lines are
> > passed unnecessarily on the system bus when these arrays are
> > referenced by cpus on other nodes.
>
> Can we move cpuinfo_x86 also to per cpu area? Though critical run
I worry how much impact that would be? boot_cpu_data is quite
widely used.
> Wonder if this confusion is the reason for git commit f3fa8ebc
What git commit (full id) ?
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-08-25 9:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 22:26 travis
2007-08-24 22:26 ` [PATCH 1/6] x86: fix cpu_to_node references (v2) travis
2007-08-25 0:23 ` Siddha, Suresh B
2007-08-27 19:47 ` Mike Travis
2007-08-24 22:26 ` [PATCH 2/6] x86: Convert cpu_core_map to be a per cpu variable (v2) travis
2007-08-24 22:26 ` [PATCH 3/6] x86: Convert cpu_sibling_map " travis
2007-09-01 2:49 ` Andrew Morton
2007-09-01 11:34 ` Kamalesh Babulal
2007-09-01 16:10 ` Andrew Morton
2007-09-02 11:48 ` Kamalesh Babulal
2007-09-01 14:06 ` Andi Kleen
2007-08-24 22:26 ` [PATCH 4/6] x86: Convert x86_cpu_to_apicid " travis
2007-08-24 22:26 ` [PATCH 5/6] x86: Convert cpu_llc_id " travis
2007-08-24 22:27 ` [PATCH 6/6] x86: acpi-use-cpu_physical_id (v2) travis
2007-08-25 0:50 ` [PATCH 0/6] x86: Reduce Memory Usage and Inter-Node message traffic (v2) Siddha, Suresh B
2007-08-25 9:24 ` Andi Kleen [this message]
2007-08-25 16:52 ` Randy Dunlap
2007-08-27 18:46 ` Mike Travis
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=20070825092434.GE16227@bingen.suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=suresh.b.siddha@intel.com \
--cc=travis@sgi.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