On Thu, May 1, 2008 at 8:09 AM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
quoted text
> On Thu, 1 May 2008 01:00:34 -0700 Yinghai Lu wrote:
>
>  >
>  > loop mtrr chunk_size and gran_size from 1M to 2G to find out optimal value.
>
>  What size step (increment) is used for these loops?
>
>
>  > so user don't need to add mtrr_chunk_size and mtrr_gran_size,
>  >
>  > if optimal value is not found, print out all list to help select less optimal
>  > value.
>  >
>  > add mtrr_spare_reg_nr= so user could set 2 instead of 1, if the card need more entries.
>  >
>  > Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
>  >
>
>
> > Index: linux-2.6/Documentation/kernel-parameters.txt
>  > ===================================================================
>  > --- linux-2.6.orig/Documentation/kernel-parameters.txt
>  > +++ linux-2.6/Documentation/kernel-parameters.txt
>  > @@ -613,9 +613,17 @@ and is between 256 and 4096 characters.
>  >                       that could hold holes aka. UC entries.
>  >
>  >       mtrr_gran_size=nn[KMG] [X86]
>  > -                     used for mtrr cleanup. It is granity of mtrr block.
>  > +                     used for mtrr cleanup. It is granularity of mtrr block.
>  > +                     default is 1.
>
>                         Default
>
>
>  >                       Big value could prevent small alignment use up MTRRs.
>
>                         Large value could prevent small alignment from
>                         using up MTRRs.
>
>
>  >
>  > +     mtrr_spare_reg_nr=n [X86]
>  > +                     Format: <integer>
>  > +                     range: 0,7 : spare reg number
>  > +                     default : 1
>  > +                     used for mtrr cleanup. It is spare mtrr entries number.
>
>                         Used
>
>
>  > +                     set to 2 or more if your graphical card need more.
>
>                         Set                                     needs more.
>
>
>  > +
>  >       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
>

Ingo, can you change that directly in the patch?
or need me send another updated patch?

YH
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/