From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: Andy Whitcroft <apw@shadowen.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org,
lhms-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/4] Memory Add Fixes for ppc64
Date: Tue, 08 Nov 2005 11:35:00 +1100 [thread overview]
Message-ID: <1131410101.4652.75.camel@gaston> (raw)
In-Reply-To: <20051107214859.GD5821@w-mikek2.ibm.com>
On Mon, 2005-11-07 at 13:48 -0800, Mike Kravetz wrote:
> On Tue, Nov 08, 2005 at 08:12:56AM +1100, Benjamin Herrenschmidt wrote:
> > Yes, the MAX_ORDER should be different indeed. But can Kconfig do that ?
> > That is have the default value be different based on a Kconfig option ?
> > I don't see that ... We may have to do things differently here...
>
> This seems to be done in other parts of the Kconfig file. Using those
> as an example, this should keep the MAX_ORDER block size at 16MB.
Ok, I verified it does the right thing with Kconfig, thanks.
Paul, can you add to the merge tree too ?
Ben.
next prev parent reply other threads:[~2005-11-08 0:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 23:15 [PATCH 0/4] " Mike Kravetz
2005-11-04 23:18 ` [PATCH 1/4] " Mike Kravetz
2005-11-05 0:04 ` Benjamin Herrenschmidt
2005-11-05 0:35 ` Mike Kravetz
2005-11-05 0:43 ` Benjamin Herrenschmidt
2005-11-07 20:47 ` Mike Kravetz
2005-11-07 21:12 ` Benjamin Herrenschmidt
2005-11-07 21:48 ` Mike Kravetz
2005-11-08 0:35 ` Benjamin Herrenschmidt [this message]
2005-11-08 14:51 ` Andy Whitcroft
2005-11-08 0:25 ` [PATCH 1/4] revised " Mike Kravetz
2005-11-08 2:07 ` Paul Mackerras
2005-11-08 3:02 ` Mike Kravetz
2005-11-04 23:19 ` [PATCH 2/4] " Mike Kravetz
2005-11-04 23:20 ` [PATCH 3/4] " Mike Kravetz
2005-11-04 23:21 ` [PATCH 4/4] " Mike Kravetz
2005-11-07 0:59 ` Paul Mackerras
2005-11-07 17:39 ` Mike Kravetz
2005-11-08 0:39 ` [PATCH 0/4] " Anton Blanchard
2005-11-08 0:48 ` Mike Kravetz
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=1131410101.4652.75.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=apw@shadowen.org \
--cc=kravetz@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-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
Powered by JetHome