From: Randy Dunlap <rdunlap@xenotime.net>
To: "Yinghai Lu" <yinghai@kernel.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] x86: mtrr_cleanup update command line
Date: Thu, 9 Oct 2008 10:20:49 -0700 [thread overview]
Message-ID: <20081009102049.c22cf670.rdunlap@xenotime.net> (raw)
In-Reply-To: <86802c440810081828m2b9210e6y81503bdffe12fb03@mail.gmail.com>
On Wed, 8 Oct 2008 18:28:39 -0700 Yinghai Lu wrote:
> On Wed, Oct 8, 2008 at 5:07 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > On Tue, 30 Sep 2008 16:57:39 -0700 Randy Dunlap wrote:
> >
> > BTW, this comment is alread in Documentation/kernel-parameters.txt, at the top of the file:
>
> oh...
>
> >
> > The following is a consolidated list of the kernel parameters as implemented
> > (mostly) by the __setup() macro and sorted into English Dictionary order
> > (defined as ignoring all punctuation and sorting digits before letters in a
> > case insensitive manner), and with descriptions where known.
> >
> >
> how about
>
> like to filter out disable, enable, no, etc...
I don't think that mtrr gets any special treatment here.
All "acpi" parameters are not grouped together (unless they begin with
"acpi"). All "apic" parameters are not grouped together.
All "*iommu*" parameters are not grouped together....
> diff --git a/Documentation/kernel-parameters.txt
> b/Documentation/kernel-parameters.txt
> index 4b9ee9b..782e2b0 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -620,35 +620,6 @@ and is between 256 and 4096 characters. It is
> defined in the file
> 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 granularity of mtrr block.
> - Default is 1.
> - 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.
> - Set to 2 or more if your graphical card 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
> - MTRR settings. This parameter disables that behavior,
> - possibly causing your machine to run very slowly.
> -
> dmasound= [HW,OSS] Sound subsystem buffers
>
> dscc4.setup= [NET]
> @@ -1310,6 +1281,35 @@ and is between 256 and 4096 characters. It is
> defined in the file
> [HW] Make the MicroTouch USB driver use raw coordinates
> ('y', default) or cooked coordinates ('n')
>
> + 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 granularity of mtrr block.
> + Default is 1.
> + 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.
> + Set to 2 or more if your graphical card 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
> + MTRR settings. This parameter disables that behavior,
> + possibly causing your machine to run very slowly.
> +
> n2= [NET] SDL Inc. RISCom/N2 synchronous serial card
>
> NCR_D700= [HW,SCSI]
>
---
~Randy
next prev parent reply other threads:[~2008-10-09 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 23:29 Yinghai Lu
2008-09-30 23:29 ` [PATCH 2/3] x86: doc mtrr-cleanup-debug Yinghai Lu
2008-09-30 23:29 ` [PATCH 3/3] x86: change MTRR_SANITIZER to def_bool y Yinghai Lu
2008-10-01 6:36 ` Ingo Molnar
2008-10-01 6:46 ` Yinghai Lu
2008-10-01 7:24 ` J.A. Magallón
2008-09-30 23:57 ` [PATCH 1/3] x86: mtrr_cleanup update command line Randy Dunlap
2008-09-30 23:41 ` H. Peter Anvin
2008-09-30 23:52 ` Yinghai Lu
2008-09-30 23:59 ` Yinghai Lu
2008-10-01 0:35 ` Randy Dunlap
2008-10-01 0:41 ` Randy Dunlap
2008-10-01 0:07 ` Randy Dunlap
2008-10-09 0:07 ` Randy Dunlap
2008-10-09 1:28 ` Yinghai Lu
2008-10-09 17:20 ` Randy Dunlap [this message]
2008-10-09 18:08 ` Yinghai Lu
2008-10-09 18:43 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081009102049.c22cf670.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®