From: Andi Kleen <ak@suse.de>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andrew Morton <akpm@osdl.org>, Jan Beulich <JBeulich@novell.com>,
linux-kernel@vger.kernel.org, shai@scalex86.org,
kiran@scalex86.org, pravins@calsoftinc.com
Subject: Re: [PATCH] [SMP] reduce size of percpudata, and make sure per_cpu(object, not_possible_cpu) cause an invalid memory reference
Date: Tue, 24 Jan 2006 15:53:50 +0100 [thread overview]
Message-ID: <200601241553.50874.ak@suse.de> (raw)
In-Reply-To: <43D63DB5.3010601@cosmosbay.com>
On Tuesday 24 January 2006 15:46, Eric Dumazet wrote:
> As some architectures (x86_64) are now allocating cpudata only on possible
> cpus, we (kernel developers on x86 machines) should make sure that x86 does
> a similar thing to find bugs. This is important that this patch has some
> exposure in -mm for some time, some places must now use :
The for_each_cpu changes should be actually merged ASAP because x86-64
needs them (or maybe i should back out that change until the kernel is ready?)
But it really saves a lot of memory - several MB on a distro kernel which is
compiled with NR_CPUS==128.
-Andi
next prev parent reply other threads:[~2006-01-24 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 13:11 [PATCH] tvec_bases too large for per-cpu data Jan Beulich
2006-01-21 7:25 ` Andrew Morton
2006-01-23 10:31 ` Jan Beulich
2006-01-23 10:57 ` Andrew Morton
2006-01-24 8:33 ` Jan Beulich
2006-01-24 8:58 ` Andrew Morton
2006-01-24 14:46 ` [PATCH] [SMP] reduce size of percpudata, and make sure per_cpu(object, not_possible_cpu) cause an invalid memory reference Eric Dumazet
2006-01-24 14:53 ` Andi Kleen [this message]
2006-02-01 9:21 ` [PATCH] [SMP] __GENERIC_PER_CPU changes Eric Dumazet
2006-01-30 8:43 ` [PATCH] tvec_bases too large for per-cpu data Jan Beulich
2006-01-31 22:27 ` 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=200601241553.50874.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=akpm@osdl.org \
--cc=dada1@cosmosbay.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pravins@calsoftinc.com \
--cc=shai@scalex86.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