* [PATCH]: expose FORCE_MAX_ZONEORDER on x86
@ 2011-10-27 9:02 Marc Leeman
2011-10-27 23:28 ` Mike Frysinger
2011-12-05 12:51 ` Ingo Molnar
0 siblings, 2 replies; 5+ messages in thread
From: Marc Leeman @ 2011-10-27 9:02 UTC (permalink / raw)
To: linux-kernel; +Cc: tglx, mingo, hpa, x86
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Larger blocks of memory can be required for e.g. higher resolutions on
some capture card drivers; this patch just enables an already
available configuration option on x86 (it was already exposed on other
architectures).
The default is set to 11, as in
./include/linux/mmzone.h
[barco@nmgserver001 linux-3.0]$ find . -name Kconfig | xargs grep
FORCE_MAX_ZONEORDER
./arch/ia64/Kconfig:config FORCE_MAX_ZONEORDER
./arch/cris/Kconfig:config FORCE_MAX_ZONEORDER
./arch/arm/Kconfig:config FORCE_MAX_ZONEORDER
./arch/s390/Kconfig:config FORCE_MAX_ZONEORDER
./arch/mips/Kconfig:config FORCE_MAX_ZONEORDER
./arch/sh/mm/Kconfig:config FORCE_MAX_ZONEORDER
./arch/blackfin/Kconfig:config FORCE_MAX_ZONEORDER
./arch/powerpc/Kconfig:config FORCE_MAX_ZONEORDER
--
br, marc
The best approach for you requires two steps. The first step is
reading the Manual.
Wolfgang Denk - u-boot mailing list
[-- Attachment #2: 0001-KConfig-x86-enable-FORCE_MAX_ZONEORDER.patch --]
[-- Type: text/x-patch, Size: 1227 bytes --]
From 8ad64edbf92ac8e0253677bd3f9ad376ce3be7d1 Mon Sep 17 00:00:00 2001
From: Marc Leeman <marc.leeman@gmail.com>
Date: Wed, 26 Oct 2011 10:35:24 +0200
Subject: [PATCH] KConfig x86: enable FORCE_MAX_ZONEORDER
---
arch/x86/Kconfig | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 9a4a267..68a98e8 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1273,6 +1273,22 @@ config ILLEGAL_POINTER_VALUE
source "mm/Kconfig"
+config FORCE_MAX_ZONEORDER
+ int "Maximum zone order"
+ range 11 64
+ default "11"
+ help
+ The kernel memory allocator divides physically contiguous memory
+ blocks into "zones", where each zone is a power of two number of
+ pages. This option selects the largest power of two that the kernel
+ keeps in the memory allocator. If you need to allocate very large
+ blocks of physically contiguous memory, then you may need to
+ increase this value.
+
+ This config option is actually maximum order plus one. For example,
+ a value of 11 means that the largest free memory block is 2^10 pages.
+
+
config HIGHPTE
bool "Allocate 3rd-level pagetables from highmem"
depends on HIGHMEM
--
1.7.2.5
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH]: expose FORCE_MAX_ZONEORDER on x86
2011-10-27 9:02 [PATCH]: expose FORCE_MAX_ZONEORDER on x86 Marc Leeman
@ 2011-10-27 23:28 ` Mike Frysinger
2011-12-05 12:51 ` Ingo Molnar
1 sibling, 0 replies; 5+ messages in thread
From: Mike Frysinger @ 2011-10-27 23:28 UTC (permalink / raw)
To: Marc Leeman; +Cc: linux-kernel, tglx, mingo, hpa, x86
On Thu, Oct 27, 2011 at 11:02, Marc Leeman <marc.leeman@gmail.com> wrote:
> Larger blocks of memory can be required for e.g. higher resolutions on
> some capture card drivers; this patch just enables an already
> available configuration option on x86 (it was already exposed on other
> architectures).
at this point, it sounds like maybe we should make it available to
everyone. perhaps under the embedded/expert/whatever-it's-called-now
sub-menu.
-mike
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH]: expose FORCE_MAX_ZONEORDER on x86
2011-10-27 9:02 [PATCH]: expose FORCE_MAX_ZONEORDER on x86 Marc Leeman
2011-10-27 23:28 ` Mike Frysinger
@ 2011-12-05 12:51 ` Ingo Molnar
2012-04-05 12:43 ` Marc Leeman
1 sibling, 1 reply; 5+ messages in thread
From: Ingo Molnar @ 2011-12-05 12:51 UTC (permalink / raw)
To: Marc Leeman; +Cc: linux-kernel, tglx, mingo, hpa, x86
* Marc Leeman <marc.leeman@gmail.com> wrote:
> Larger blocks of memory can be required for e.g. higher resolutions on
> some capture card drivers; this patch just enables an already
> available configuration option on x86 (it was already exposed on other
> architectures).
>
> The default is set to 11, as in
> ./include/linux/mmzone.h
>
> [barco@nmgserver001 linux-3.0]$ find . -name Kconfig | xargs grep
> FORCE_MAX_ZONEORDER
> ./arch/ia64/Kconfig:config FORCE_MAX_ZONEORDER
> ./arch/cris/Kconfig:config FORCE_MAX_ZONEORDER
> ./arch/arm/Kconfig:config FORCE_MAX_ZONEORDER
> ./arch/s390/Kconfig:config FORCE_MAX_ZONEORDER
> ./arch/mips/Kconfig:config FORCE_MAX_ZONEORDER
> ./arch/sh/mm/Kconfig:config FORCE_MAX_ZONEORDER
> ./arch/blackfin/Kconfig:config FORCE_MAX_ZONEORDER
> ./arch/powerpc/Kconfig:config FORCE_MAX_ZONEORDER
>
>
>
> --
> br, marc
>
> The best approach for you requires two steps. The first step is
> reading the Manual.
> Wolfgang Denk - u-boot mailing list
> From 8ad64edbf92ac8e0253677bd3f9ad376ce3be7d1 Mon Sep 17 00:00:00 2001
> From: Marc Leeman <marc.leeman@gmail.com>
> Date: Wed, 26 Oct 2011 10:35:24 +0200
> Subject: [PATCH] KConfig x86: enable FORCE_MAX_ZONEORDER
I guess we could do this - but you forgot to sign off on your
patch.
Thanks,
Ingo
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH]: expose FORCE_MAX_ZONEORDER on x86
2011-12-05 12:51 ` Ingo Molnar
@ 2012-04-05 12:43 ` Marc Leeman
2012-04-05 13:37 ` Marc Leeman
0 siblings, 1 reply; 5+ messages in thread
From: Marc Leeman @ 2012-04-05 12:43 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Marc Leeman, linux-kernel, tglx, mingo, hpa, x86
[-- Attachment #1.1: Type: text/plain, Size: 240 bytes --]
> I guess we could do this - but you forgot to sign off on your
> patch.
It took me some time, but I finally rebased the patch against 3.3
--
greetz, marc
harvey 2.6.29.1 #1 PREEMPT Mon Apr 6 22:33:31 CDT 2009 GNU/Linux
[-- Attachment #1.2: 0001-KConfig-x86-enable-FORCE_MAX_ZONEORDER.patch --]
[-- Type: text/x-diff, Size: 2089 bytes --]
From 8ad64edbf92ac8e0253677bd3f9ad376ce3be7d1 Mon Sep 17 00:00:00 2001
From: Marc Leeman <marc.leeman@gmail.com>
Date: Wed, 26 Oct 2011 10:35:24 +0200
Subject: [PATCH 3.3] KConfig x86: enable FORCE_MAX_ZONEORDER
Larger blocks of memory can be required for e.g. higher resolutions on
some capture card drivers; this patch just enables an already
available configuration option on x86 (it was already exposed on other
architectures).
The default is set to 11, as in
./include/linux/mmzone.h
[barco@nmgserver001 linux-3.0]$ find . -name Kconfig | xargs grep FORCE_MAX_ZONEORDER
./arch/ia64/Kconfig:config FORCE_MAX_ZONEORDER
./arch/cris/Kconfig:config FORCE_MAX_ZONEORDER
./arch/arm/Kconfig:config FORCE_MAX_ZONEORDER
./arch/s390/Kconfig:config FORCE_MAX_ZONEORDER
./arch/mips/Kconfig:config FORCE_MAX_ZONEORDER
./arch/sh/mm/Kconfig:config FORCE_MAX_ZONEORDER
./arch/blackfin/Kconfig:config FORCE_MAX_ZONEORDER
./arch/powerpc/Kconfig:config FORCE_MAX_ZONEORDER
Signed-off-by: Marc Leeman <marc.leeman@gmail.com>
---
arch/x86/Kconfig | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 9a4a267..68a98e8 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1312,6 +1312,22 @@ config ILLEGAL_POINTER_VALUE
source "mm/Kconfig"
+config FORCE_MAX_ZONEORDER
+ int "Maximum zone order"
+ range 11 64
+ default "11"
+ help
+ The kernel memory allocator divides physically contiguous memory
+ blocks into "zones", where each zone is a power of two number of
+ pages. This option selects the largest power of two that the kernel
+ keeps in the memory allocator. If you need to allocate very large
+ blocks of physically contiguous memory, then you may need to
+ increase this value.
+
+ This config option is actually maximum order plus one. For example,
+ a value of 11 means that the largest free memory block is 2^10 pages.
+
+
config HIGHPTE
bool "Allocate 3rd-level pagetables from highmem"
depends on HIGHMEM
--
1.7.2.5
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH]: expose FORCE_MAX_ZONEORDER on x86
2012-04-05 12:43 ` Marc Leeman
@ 2012-04-05 13:37 ` Marc Leeman
0 siblings, 0 replies; 5+ messages in thread
From: Marc Leeman @ 2012-04-05 13:37 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Marc Leeman, linux-kernel, tglx, mingo, hpa, x86
[-- Attachment #1.1: Type: text/plain, Size: 322 bytes --]
> > I guess we could do this - but you forgot to sign off on your
> > patch.
>
> It took me some time, but I finally rebased the patch against 3.3
Sorry, the previous patch gave a (sloppy) whitespace warning, refreshed
it.
--
greetz, marc
harvey 2.6.29.1 #1 PREEMPT Mon Apr 6 22:33:31 CDT 2009 GNU/Linux
[-- Attachment #1.2: 0001-KConfig-x86-enable-FORCE_MAX_ZONEORDER-updated.patch --]
[-- Type: text/x-diff, Size: 2078 bytes --]
From 463bf232150089ee114ebc9712890ff5b0aca9c5 Mon Sep 17 00:00:00 2001
From: Marc Leeman <marc.leeman@gmail.com>
Date: Thu, 5 Apr 2012 14:25:22 +0200
Subject: KConfig x86: enable FORCE_MAX_ZONEORDER
Larger blocks of memory can be required for e.g. higher resolutions on
some capture card drivers; this patch just enables an already
available configuration option on x86 (it was already exposed on other
architectures).
The default is set to 11, as in
./include/linux/mmzone.h
[barco@nmgserver001 linux-3.0]$ find . -name Kconfig | xargs grep FORCE_MAX_ZONEORDER
./arch/ia64/Kconfig:config FORCE_MAX_ZONEORDER
./arch/cris/Kconfig:config FORCE_MAX_ZONEORDER
./arch/arm/Kconfig:config FORCE_MAX_ZONEORDER
./arch/s390/Kconfig:config FORCE_MAX_ZONEORDER
./arch/mips/Kconfig:config FORCE_MAX_ZONEORDER
./arch/sh/mm/Kconfig:config FORCE_MAX_ZONEORDER
./arch/blackfin/Kconfig:config FORCE_MAX_ZONEORDER
./arch/powerpc/Kconfig:config FORCE_MAX_ZONEORDER
Signed-off-by: Marc Leeman <marc.leeman@barco.com>
---
arch/x86/Kconfig | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 1d14cc6..ba4ed6a 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1296,6 +1296,22 @@ config ILLEGAL_POINTER_VALUE
source "mm/Kconfig"
+config FORCE_MAX_ZONEORDER
+ int "Maximum zone order"
+ range 11 64
+ default "11"
+ help
+ The kernel memory allocator divides physically contiguous memory
+ blocks into "zones", where each zone is a power of two number of
+ pages. This option selects the largest power of two that the kernel
+ keeps in the memory allocator. If you need to allocate very large
+ blocks of physically contiguous memory, then you may need to
+ increase this value.
+
+ This config option is actually maximum order plus one. For example,
+ a value of 11 means that the largest free memory block is 2^10 pages.
+
+
config HIGHPTE
bool "Allocate 3rd-level pagetables from highmem"
depends on HIGHMEM
--
1.7.2.5
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-04-05 13:37 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-10-27 9:02 [PATCH]: expose FORCE_MAX_ZONEORDER on x86 Marc Leeman
2011-10-27 23:28 ` Mike Frysinger
2011-12-05 12:51 ` Ingo Molnar
2012-04-05 12:43 ` Marc Leeman
2012-04-05 13:37 ` Marc Leeman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®