mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Marc Leeman <marc.leeman@gmail.com>
Cc: 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: Mon, 5 Dec 2011 13:51:07 +0100	[thread overview]
Message-ID: <20111205125107.GH3143@elte.hu> (raw)
In-Reply-To: <CAH+fs=-WkbLgB-wsNEPS_OnvqwK9eChMCrMOudjtg7bu2ZtqHg@mail.gmail.com>


* 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

  parent reply	other threads:[~2011-12-05 12:52 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 [this message]
2012-04-05 12:43   ` Marc Leeman
2012-04-05 13:37     ` Marc Leeman

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=20111205125107.GH3143@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.leeman@gmail.com \
    --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®