From: Joerg Roedel <joerg.roedel@amd.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: andreas.herrmann3@amd.com, tglx@linutronix.de, mingo@elte.hu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [4/7] Don't use large pages to map the first 2/4MB of memory
Date: Tue, 25 Mar 2008 12:31:23 +0100 [thread overview]
Message-ID: <20080325113123.GL17986@amd.com> (raw)
In-Reply-To: <20080312025330.AC1961B41D1@basil.firstfloor.org>
On Wed, Mar 12, 2008 at 03:53:30AM +0100, Andi Kleen wrote:
>
> Intel recommends to not use large pages for the first 1MB
> of the physical memory because there are fixed size MTRRs there
> which cause splitups in the TLBs.
>
> On AMD doing so is also a good idea.
This should especially boost performance on 32 bit. Have you numbers for
that?
> The implementation is a little different between 32bit and 64bit.
> On 32bit I just taught the initial page table set up about this
> because it was very simple to do. This also has the advantage
> that the risk of a prefetch ever seeing the page even
> if it only exists for a short time is minimized.
>
> On 64bit that is not quite possible, so use set_memory_4k() a little
> later (in check_bugs) instead.
>
> Signed-off-by: Andi Kleen <ak@suse.de>
Acked-by: Joerg Roedel <joerg.roedel@amd.com>
> ---
> arch/x86/kernel/bugs_64.c | 12 ++++++++++++
> arch/x86/mm/init_32.c | 6 +++++-
> 2 files changed, 17 insertions(+), 1 deletion(-)
>
> Index: linux/arch/x86/kernel/bugs_64.c
> ===================================================================
> --- linux.orig/arch/x86/kernel/bugs_64.c
> +++ linux/arch/x86/kernel/bugs_64.c
> @@ -9,6 +9,7 @@
> #include <asm/bugs.h>
> #include <asm/processor.h>
> #include <asm/mtrr.h>
> +#include <asm/cacheflush.h>
>
> void __init check_bugs(void)
> {
> @@ -18,4 +19,15 @@ void __init check_bugs(void)
> print_cpu_info(&boot_cpu_data);
> #endif
> alternative_instructions();
> +
> + /*
> + * Make sure the first 2MB area is not mapped by huge pages
> + * There are typically fixed size MTRRs in there and overlapping
> + * MTRRs into large pages causes slow downs.
> + *
> + * Right now we don't do that with gbpages because there seems
> + * very little benefit for that case.
> + */
> + if (!direct_gbpages)
> + set_memory_4k((unsigned long)__va(0), 1);
> }
> Index: linux/arch/x86/mm/init_32.c
> ===================================================================
> --- linux.orig/arch/x86/mm/init_32.c
> +++ linux/arch/x86/mm/init_32.c
> @@ -181,8 +181,13 @@ static void __init kernel_physical_mappi
> /*
> * Map with big pages if possible, otherwise
> * create normal page tables:
> + *
> + * Don't use a large page for the first 2/4MB of memory
> + * because there are often fixed size MTRRs in there
> + * and overlapping MTRRs into large pages can cause
> + * slowdowns.
> */
> - if (cpu_has_pse) {
> + if (cpu_has_pse && !(pgd_idx == 0 && pmd_idx == 0)) {
> unsigned int addr2;
> pgprot_t prot = PAGE_KERNEL_LARGE;
>
> --
> 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/
>
--
| AMD Saxony Limited Liability Company & Co. KG
Operating | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
System | Register Court Dresden: HRA 4896
Research | General Partner authorized to represent:
Center | AMD Saxony LLC (Wilmington, Delaware, US)
| General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-03-25 11:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 2:53 [PATCH] [1/7] Implement true end_pfn_mapped for 32bit Andi Kleen
2008-03-12 2:53 ` [PATCH] [2/7] Account overlapped mappings in end_pfn_map Andi Kleen
2008-03-12 2:53 ` [PATCH] [3/7] Add set_memory_4k to pageattr.c Andi Kleen
2008-03-12 2:53 ` [PATCH] [4/7] Don't use large pages to map the first 2/4MB of memory Andi Kleen
2008-03-12 5:38 ` Eric Dumazet
2008-03-12 9:19 ` Andi Kleen
2008-03-21 17:45 ` Thomas Gleixner
2008-03-21 17:59 ` Andi Kleen
2008-03-21 18:03 ` Thomas Gleixner
2008-03-21 18:44 ` Andi Kleen
2008-03-25 11:31 ` Joerg Roedel [this message]
2008-03-25 11:39 ` Andi Kleen
2008-03-12 2:53 ` [PATCH] [5/7] Readd rdmsrl_safe Andi Kleen
2008-03-21 17:06 ` Thomas Gleixner
2008-03-21 17:16 ` Andi Kleen
2008-03-21 17:58 ` Thomas Gleixner
2008-03-21 18:06 ` Andi Kleen
2008-03-21 18:14 ` Thomas Gleixner
2008-03-21 18:46 ` Andi Kleen
2008-03-21 18:48 ` [PATCH] [5/7] Readd rdmsrl_safe II Andi Kleen
2008-03-22 9:59 ` [PATCH] Readd rdmsrl_safe v2 Andi Kleen
2008-03-12 2:53 ` [PATCH] [6/7] Split large page mapping for AMD TSEG Andi Kleen
2008-03-21 17:55 ` Thomas Gleixner
2008-03-25 11:56 ` Joerg Roedel
2008-03-25 16:44 ` Thomas Gleixner
2008-03-25 16:54 ` Andi Kleen
2008-03-12 2:53 ` [PATCH] [7/7] CPA: Add statistics about state of direct mapping v2 Andi Kleen
2008-03-21 17:41 ` Thomas Gleixner
2008-03-21 17:55 ` Andi Kleen
2008-03-22 9:50 ` [PATCH] CPA: Add statistics about state of direct mapping v3 Andi Kleen
2008-03-25 15:40 ` Thomas Gleixner
2008-03-25 16:14 ` Andi Kleen
2008-03-25 16:16 ` Thomas Gleixner
2008-03-25 17:01 ` [PATCH] CPA: Add statistics about state of direct mapping v4 Andi Kleen
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=20080325113123.GL17986@amd.com \
--to=joerg.roedel@amd.com \
--cc=andi@firstfloor.org \
--cc=andreas.herrmann3@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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