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 0/1] x86: Convert cpuinfo_x86 array to a per_cpu array v3
Date: Tue, 16 Oct 2007 01:18:27 -0700 [thread overview]
Message-ID: <20071016011827.91350174.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070924210853.256462000@sgi.com>
On Mon, 24 Sep 2007 14:08:53 -0700 travis@sgi.com wrote:
>
> v3: fix compile errors in arch-i386-allmodconfig build
>
> v2: rebasing on 2.6.23-rc6-mm1
>
> Analyzing various data structures when NR_CPU count is raised
> to 4096 shows the following arrays over 128k. If the maximum
> number of cpus are not installed (about 99.99% of the time),
> then a large percentage of this memory is wasted.
> --
> 151289856 CALNDATA irq_desc
> 135530496 RMDATATA irq_cfg
> 3145728 CALNDATA cpu_data
> 2101248 BSS irq_lists
> 2097152 RMDATATA cpu_sibling_map
> 2097152 RMDATATA cpu_core_map
> 1575936 BSS irq_2_pin
> 1050624 BSS irq_timer_state
> 614400 INITDATA early_node_map
> 525376 PERCPU per_cpu__kstat
> 524608 DATA unix_proto
> 524608 DATA udpv6_prot
> 524608 DATA udplitev6_prot
> 524608 DATA udplite_prot
> 524608 DATA udp_prot
> 524608 DATA tcpv6_prot
> 524608 DATA tcp_prot
> 524608 DATA rawv6_prot
> 524608 DATA raw_prot
> 524608 DATA packet_proto
> 524608 DATA netlink_proto
> 524288 BSS cpu_devices
> 524288 BSS boot_pageset
> 524288 CALNDATA boot_cpu_pda
> 262144 RMDATATA node_to_cpumask
> 262144 BSS __log_buf
> 131072 BSS entries
>
> cpu_sibling_map and cpu_core_map have been taken care of in
> a prior patch. This patch deals with the cpu_data array of
> cpuinfo_x86 structs. The model that was used in sparc64
> architecture was adopted for x86.
>
This has mysteriously started to oops on me, only on x86_64.
http://userweb.kernel.org/~akpm/config-x.txt
http://userweb.kernel.org/~akpm/dsc00001.jpg
which is a bit strange since this patch doesn't touch sched.c. Maybe
there's something somewhere else in the -mm lineup which when combined with
this prevents it from oopsing, dunno. I'll hold it back for now and will
see what happens.
--
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-10-16 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 21:08 [PATCH 0/1] x86: Convert cpuinfo_x86 array to a per_cpu array v3 travis
2007-09-24 21:08 ` [PATCH 1/1] " travis
2007-09-24 22:01 ` roel
2007-09-24 23:24 ` Dave Jones
2007-09-25 0:20 ` roel
2007-09-25 0:31 ` Dave Jones
2007-10-16 8:18 ` Andrew Morton [this message]
2007-08-04 1:15 ` [PATCH 0/1] " Mike Travis
2007-10-16 15:02 ` Christoph Lameter
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=20071016011827.91350174.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).