lkml.org 
[lkml]   [2008]   [Apr]   [29]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateTue, 29 Apr 2008 14:54:31 -0700
From"Yinghai Lu" <>
SubjectRe: [PATCH 1/2] x86: mtrr cleanup for converting continuous to discrete layout v8
On Tue, Apr 29, 2008 at 1:46 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> 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.

thanks.

>
>  How does someone know that size/granity/whatever of an mtrr block?

considering to auto test to find optimal value for mtrr_chunk_size and
mtrr_gran_size...

YH


\
 
 \ /
  Last update: 2008-04-29 23:57    [from the cache]
©2003-2008