[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080429134617.1bc3b2d5.randy.dunlap@oracle.com>
Date: Tue, 29 Apr 2008 13:46:17 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: yhlu.kernel@...il.com
Cc: Yinghai Lu <yhlu.kernel.send@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Gabriel C <nix.or.die@...glemail.com>,
Mika Fischer <mika.fischer@...pnet.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] x86: mtrr cleanup for converting continuous to
discrete layout v8
On Tue, 29 Apr 2008 03:52:33 -0700 Yinghai Lu wrote:
> Index: linux-2.6/Documentation/kernel-parameters.txt
> ===================================================================
> --- linux-2.6.orig/Documentation/kernel-parameters.txt
> +++ linux-2.6/Documentation/kernel-parameters.txt
> @@ -595,6 +595,20 @@ and is between 256 and 4096 characters.
> See drivers/char/README.epca and
> Documentation/digiepca.txt.
>
> + disable_mtrr_cleanup [X86]
> + enable_mtrr_cleanup [X86]
> + The kernel tries to adjust MTRR layout from continuous
> + to discrete, to make X server driver able to add WB
> + entry later. This parameter enables/disables that.
> +
> + mtrr_chunk_size=nn[KMG] [X86]
> + used for mtrr cleanup. It is largest continous chunk
> + that could hold holes aka. UC entries.
> +
> + mtrr_gran_size=nn[KMG] [X86]
> + used for mtrr cleanup. It is granity of mtrr block.
s/granity/granularity/
I think that's what you mean/want.
How does someone know that size/granity/whatever of an mtrr block?
> + Big value could prevent small alignment use up MTRRs.
> +
> disable_mtrr_trim [X86, Intel and AMD only]
> By default the kernel will trim any uncacheable
> memory out of your available memory pool based on
---
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists