diff options
| author | Mike Kravetz <kravetz@us.ibm.com> | 2005-11-07 13:48:59 -0800 |
|---|---|---|
| committer | Paul Mackerras <paulus@samba.org> | 2005-11-08 11:20:00 +1100 |
| commit | 0286486783a75ef991df3ee250917efb55df75b3 (patch) | |
| tree | 067d186c3e1f79f44d9ac729cf67c898d329f2ab /arch/ppc64/Kconfig | |
| parent | 570142ca37248291c03df9852a5a0ce97f756464 (diff) | |
[PATCH] Memory Add Fixes for ppc64
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.
Signed-off-by: Mike Kravetz <kravetz@us.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'arch/ppc64/Kconfig')
| -rw-r--r-- | arch/ppc64/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/ppc64/Kconfig b/arch/ppc64/Kconfig index 94a81279dea..29552348e58 100644 --- a/arch/ppc64/Kconfig +++ b/arch/ppc64/Kconfig @@ -56,6 +56,7 @@ config PPC_STD_MMU # max order + 1 config FORCE_MAX_ZONEORDER int + default "9" if PPC_64K_PAGES default "13" source "init/Kconfig" |