From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Increase the upper bound on NR_CPUS.
Date: Thu, 29 Nov 2007 11:33:40 +0100 [thread overview]
Message-ID: <200711291133.41188.arnd@arndb.de> (raw)
In-Reply-To: <20071129041603.GM24243@bakeyournoodle.com>
On Thursday 29 November 2007, Tony Breeds wrote:
> why not?
In the past I've seen run-time problems because some parts of the
code kmalloc NR_CPUS sized arrays, which can easily grow beyond
the kmalloc limit of 128kb. Have you tried running some tests
on a small machine with the big NR_CPUS?
Arnd <><
prev parent reply other threads:[~2007-11-29 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 4:16 [PATCH] Increase the upper bound on NR_CPUS Tony Breeds
2007-11-29 4:17 ` Michael Ellerman
2007-11-29 4:23 ` Tony Breeds
2007-11-29 4:44 ` Michael Ellerman
2007-11-29 6:23 ` Stephen Rothwell
2007-11-29 10:33 ` Arnd Bergmann [this message]
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=200711291133.41188.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).