From: Andi Kleen <ak@muc.de>
To: mingo@elte.hu (Ingo Molnar)
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
jamesclv@us.ibm.com
Subject: Re: [PATCH] MAX_MP_BUSSES increase
Date: 20 Dec 2001 18:03:36 +0100 [thread overview]
Message-ID: <m3y9jxesd3.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0112192154190.19321-100000@penguin.transmeta.com> <Pine.LNX.4.33.0112201405550.6212-100000@localhost.localdomain>
In-Reply-To: mingo@elte.hu's message of "Thu, 20 Dec 2001 11:13:10 +0000 (UTC)"
mingo@elte.hu (Ingo Molnar) writes:
> On Wed, 19 Dec 2001, Linus Torvalds wrote:
>
> > > Marcello and Linus, please apply.
> >
> > Can you give a rough description of what kinds of arrays this will
> > impact, just out of curiosity. Ie do we talk about "5kB more memory in
> > order to avoid problems", or are we talking about something
> > noticeable..
> >
> > Linus "too lazy to grep" Torvalds
>
> the change is OK, it's about +3K RAM used, on SMP kernels.
hmm, I come more to 11K (most of it in mp_irqs)
... which could be easily allocated with the bootmem allocator at parse time.
-Andi
next prev parent reply other threads:[~2001-12-20 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 4:28 [PATCH] MAX_MP_BUSSES increase James Cleverdon
2001-12-20 5:55 ` Linus Torvalds
2001-12-20 13:07 ` Ingo Molnar
2001-12-20 17:03 ` Andi Kleen [this message]
2001-12-20 22:29 ` James Cleverdon
2001-12-20 22:56 ` Andi Kleen
[not found] ` <Pine.LNX.4.33.0112211113570.2196-100000@localhost.localdomain>
2001-12-21 9:14 ` William Lee Irwin III
2001-12-26 15:43 ` Marcelo Tosatti
2002-01-08 9:14 ` James Cleverdon
2002-01-08 9:41 ` Martin J. Bligh
2002-01-18 21:21 ` James Cleverdon
[not found] <200112210419.fBL4Jfq08533@butler1.beaverton.ibm.com>
[not found] ` <Pine.LNX.4.33.0112211131130.2269-100000@localhost.localdomain>
2001-12-21 11:57 ` William Lee Irwin III
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=m3y9jxesd3.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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