[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080208233738.108449000@polaris-admin.engr.sgi.com>
Date: Fri, 08 Feb 2008 15:37:38 -0800
From: Mike Travis <travis@....com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>, Andi Kleen <ak@...e.de>
Cc: Christoph Lameter <clameter@....com>,
Jack Steiner <steiner@....com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/4] NR_CPUS: non-x86 arch specific reduction of NR_CPUS usage
Here's another round of removing static allocations of arrays
using NR_CPUS to size the length. The change is to use PER_CPU
variables in place of the static tables.
Based on linux-2.6.git + x86.git
Cc: Dave Jones <davej@...emonkey.org.uk>
Cc: cpufreq@...ts.linux.org.uk
Cc: Len Brown <len.brown@...el.com>
Cc: linux-acpi@...r.kernel.org
Cc: Philippe Elie <phil.el@...adoo.fr>
Cc: oprofile-list@...ts.sf.net
Signed-off-by: Mike Travis <travis@....com>
---
(1 - if modules enabled, does not complete boot even
without this patch)
x86_64 configs built and booted:
ingo-stress-test(1)
defconfi
nonuma
nosmp
bigsmp (NR_CPUS=1024, 1024 possible, 8 real)
Other configs built:
arm-default
i386-default
i386-single
i386-smp
ppc-pmac32
ppc-smp
sparc64-default
sparc64-smp
x86_64-8psmp
x86_64-debug
x86_64-default
x86_64-numa
x86_64-single
x86_64-allmodconfig
x86_64-allyesconfig
x86_64-maxsmp (NR_CPUS=4096 MAXNODES=512)
Configs not built due to prior errors:
ia64-sn2
ia64-default
ia64-nosmp
ia64-zx1
s390-default
sparc-default
Memory effects using x86_64-maxsmp
Removes 1MB from permanant data adding 440 bytes to percpu area.
4k-cpus-before 4k-cpus-after
3463036 .bss -98304 -2%
6067456 .data.cacheline_alig -1048576 -17%
48712 .data.percpu +440 +0%
14275505 .text +336 +0%
14275505 Text +336 +0%
8521495 Data -336 +0%
3463036 Bss -98304 -2%
10974520 OtherData -1048576 -9%
48712 PerCpu +440 +0%
39275796 Total -1146104 -2%
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists