Re: [PATCH 1/2] x86: mtrr cleanup for converting continuous to discrete layout v8

From: Yinghai Lu
Date: Tue Apr 29 2008 - 17:54:46 EST


On Tue, Apr 29, 2008 at 1:46 PM, Randy Dunlap <randy.dunlap@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/