lkml.org 
[lkml]   [2008]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [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


\
 
 \ /
  Last update: 2008-04-29 22:51    [W:0.150 / U:0.316 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site