From: Andrew Morton <akpm@linux-foundation.org>
To: travis@sgi.com
Cc: Andi Kleen <ak@suse.de>, Christoph Lameter <clameter@sgi.com>,
Jack Steiner <steiner@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2
Date: Fri, 21 Sep 2007 15:46:22 -0700 [thread overview]
Message-ID: <20070921154622.c6920dcf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070920213004.781159000@sgi.com>
On Thu, 20 Sep 2007 14:30:05 -0700
travis@sgi.com wrote:
> cpu_data is currently an array defined using NR_CPUS. This means that
> we overallocate since we will rarely really use maximum configured cpus.
> When NR_CPU count is raised to 4096 the size of cpu_data becomes
> 3,145,728 bytes.
This has at least three quite obvious and careless compilation errors.
Please at least compile the code after you've altered it.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: travis@sgi.com
Cc: Andi Kleen <ak@suse.de>, Christoph Lameter <clameter@sgi.com>,
Jack Steiner <steiner@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2
Date: Fri, 21 Sep 2007 15:46:22 -0700 [thread overview]
Message-ID: <20070921154622.c6920dcf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070920213004.781159000@sgi.com>
On Thu, 20 Sep 2007 14:30:05 -0700
travis@sgi.com wrote:
> cpu_data is currently an array defined using NR_CPUS. This means that
> we overallocate since we will rarely really use maximum configured cpus.
> When NR_CPU count is raised to 4096 the size of cpu_data becomes
> 3,145,728 bytes.
This has at least three quite obvious and careless compilation errors.
Please at least compile the code after you've altered it.
--
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-09-21 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 21:30 [PATCH 0/1] x86: Reduce Memory Usage for large CPU count systems v2 travis
2007-09-20 21:30 ` travis
2007-09-20 21:30 ` [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2 travis
2007-09-20 21:30 ` travis
2007-09-21 22:46 ` Andrew Morton [this message]
2007-09-21 22:46 ` Andrew Morton
2007-09-24 17:22 ` Mike Travis
2007-09-24 17:22 ` Mike Travis
2007-09-21 10:16 ` [PATCH 0/1] x86: Reduce Memory Usage for large CPU count systems v2 Andrew Morton
2007-09-21 10:16 ` Andrew Morton
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=20070921154622.c6920dcf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=steiner@sgi.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 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.