From: tony@bakeyournoodle.com (Tony Breeds)
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/3 v3] Raise the upper limit of NR_CPUS.
Date: Wed, 23 Apr 2008 16:08:36 +1000 [thread overview]
Message-ID: <20080423060836.GM20457@bakeyournoodle.com> (raw)
In-Reply-To: <1208929299.9212.4.camel@concordia.ozlabs.ibm.com>
On Wed, Apr 23, 2008 at 03:41:39PM +1000, Michael Ellerman wrote:
> You add about 30 lines of code in this patch, which you remove in patch
> 3, is there a better way to do it?
>
> Is there any harm dynamically initialising the statically initialised
> pacas, I think that would allow you to basically skip the
> NR_STATIC_PACAS business.
Yes, I could make patch 2 the first in the series, and then roll batches
1 and 3 together. As iSeries will barf I do all the PACAs dynamically
without that extra wait.
/me is too linear.
new version comming.
Yours Tony
linux.conf.au http://www.marchsouth.org/
Jan 19 - 24 2009 The Australian Linux Technical Conference!
prev parent reply other threads:[~2008-04-23 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 4:06 [PATCH 1/3 v3] Raise the upper limit of NR_CPUS Tony Breeds
2008-04-23 4:06 ` [PATCH 2/3 v3] Make iSeries spin on __secondary_hold_spinloop, like pSeries Tony Breeds
2008-04-23 4:06 ` [PATCH 3/3 v3] Move the paca array into the BSS Tony Breeds
2008-04-23 5:41 ` [PATCH 1/3 v3] Raise the upper limit of NR_CPUS Michael Ellerman
2008-04-23 6:08 ` Tony Breeds [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=20080423060836.GM20457@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--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