public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] x86: enable GBPAGES option by default
Date: Wed, 22 Oct 2008 12:35:12 +0200	[thread overview]
Message-ID: <20081022103512.GA1928@wotan.suse.de> (raw)
In-Reply-To: <20081022103316.GB27862@wotan.suse.de>

Oops, messed up Andi's email...

On Wed, Oct 22, 2008 at 12:33:16PM +0200, Nick Piggin wrote:
> DIRECT_GBPAGES was under DEBUG_KERNEL && EXPERIMENTAL and disabled by default.
> Turn it on by default and put it under EMBEDDED.
> 
> Signed-off-by: Nick Piggin <npiggin@suse.de>
> ---
> Index: linux-2.6/arch/x86/Kconfig
> ===================================================================
> --- linux-2.6.orig/arch/x86/Kconfig
> +++ linux-2.6/arch/x86/Kconfig
> @@ -946,6 +946,15 @@ config X86_PAE
>  config ARCH_PHYS_ADDR_T_64BIT
>         def_bool X86_64 || X86_PAE
>  
> +config DIRECT_GBPAGES
> +	bool "Enable 1GB pages for kernel pagetables" if EMBEDDED
> +	default y
> +	depends on X86_64
> +	help
> +	  Allow the kernel linear mapping to use 1GB pages on CPUs that
> +	  support it. This can improve the kernel's performance a tiny bit by
> +	  reducing TLB pressure. If in doubt, say "Y".
> +
>  # Common NUMA Features
>  config NUMA
>  	bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
> Index: linux-2.6/arch/x86/Kconfig.debug
> ===================================================================
> --- linux-2.6.orig/arch/x86/Kconfig.debug
> +++ linux-2.6/arch/x86/Kconfig.debug
> @@ -114,18 +114,6 @@ config DEBUG_RODATA
>  	  data. This is recommended so that we can catch kernel bugs sooner.
>  	  If in doubt, say "Y".
>  
> -config DIRECT_GBPAGES
> -	bool "Enable gbpages-mapped kernel pagetables"
> -	depends on DEBUG_KERNEL && EXPERIMENTAL && X86_64
> -	help
> -	  Enable gigabyte pages support (if the CPU supports it). This can
> -	  improve the kernel's performance a tiny bit by reducing TLB
> -	  pressure.
> -
> -	  This is experimental code.
> -
> -	  If in doubt, say "N".
> -
>  config DEBUG_RODATA_TEST
>  	bool "Testcase for the DEBUG_RODATA feature"
>  	depends on DEBUG_RODATA

  reply	other threads:[~2008-10-22 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 10:33 [patch] x86: enable GBPAGES option by default Nick Piggin
2008-10-22 10:35 ` Nick Piggin [this message]
2008-10-22 11:30 ` Ingo Molnar

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=20081022103512.GA1928@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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