From: Marc Leeman <marc.leeman@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Marc Leeman <marc.leeman@gmail.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH]: expose FORCE_MAX_ZONEORDER on x86
Date: Thu, 5 Apr 2012 15:37:27 +0200 [thread overview]
Message-ID: <20120405133726.GS2473@scorpius.homelinux.org> (raw)
In-Reply-To: <20120405124322.GQ2473@scorpius.homelinux.org>
[-- 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 --]
prev parent reply other threads:[~2012-04-05 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 9:02 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 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=20120405133726.GS2473@scorpius.homelinux.org \
--to=marc.leeman@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®