64 bit: Set up a cpu area that allows the use of up 16MB for each processor. Cpu memory use can grow a bit. F.e. if we assume that a pageset occupies 64 bytes of memory and we have 3 zones in each of 1024 nodes then we need 3 * 1k * 16k = 50 million pagesets or 3096 pagesets per processor. This results in a total of 3.2 GB of page structs. Each cpu needs around 200k of cpu storage for the page allocator alone. So its a worth it to use a 2M huge mapping here. For the UP and SMP case map the area using 4k ptes. Typical use of per cpu data is around 16k for UP and SMP configurations. It goes up to 45k when the per cpu area is managed by cpu_alloc (see special x86_64 patchset). Allocating in 2M segments would be overkill. For NUMA map the area using 2M PMDs. A large NUMA system may use lots of cpu data for the page allocator data alone. We typically have large amounts of memory around on those size. Using a 2M page size reduces TLB pressure for that case. Some numbers for envisioned maximum configurations of NUMA systems: 4k cpu configurations with 1k nodes: 4096 * 16MB = 64TB of virtual space. Maximum theoretical configuration 16384 processors 1k nodes: 16384 * 16MB = 256TB of virtual space. Both fit within the established limits established. 32 bit: Setup a 256 kB area for the cpu areas below the FIXADDR area. The use of the cpu alloc area is pretty minimal on i386. An 8p system with no extras uses only ~8kb. So 256kb should be plenty. A configuration that supports up to 8 processors takes up 2MB of the scarce virtual address space Signed-off-by: Christoph Lameter --- arch/x86/Kconfig | 15 +++++++++++++++ arch/x86/mm/init_32.c | 3 +++ arch/x86/mm/init_64.c | 38 ++++++++++++++++++++++++++++++++++++++ include/asm-x86/pgtable_32.h | 7 +++++-- include/asm-x86/pgtable_64.h | 1 + 5 files changed, 62 insertions(+), 2 deletions(-) Index: linux-2.6/arch/x86/mm/init_64.c =================================================================== --- linux-2.6.orig/arch/x86/mm/init_64.c 2007-11-15 21:24:47.059904335 -0800 +++ linux-2.6/arch/x86/mm/init_64.c 2007-11-15 21:25:18.578584246 -0800 @@ -781,3 +781,41 @@ int __meminit vmemmap_populate(struct pa return 0; } #endif + +#ifdef CONFIG_NUMA +int __meminit cpu_area_populate(void *start, unsigned long size, + gfp_t flags, int node) +{ + unsigned long addr = (unsigned long)start; + unsigned long end = addr + size; + unsigned long next; + pgd_t *pgd; + pud_t *pud; + pmd_t *pmd; + + for (; addr < end; addr = next) { + next = pmd_addr_end(addr, end); + + pgd = cpu_area_pgd_populate(addr, flags, node); + if (!pgd) + return -ENOMEM; + pud = cpu_area_pud_populate(pgd, addr, flags, node); + if (!pud) + return -ENOMEM; + + pmd = pmd_offset(pud, addr); + if (pmd_none(*pmd)) { + pte_t entry; + void *p = cpu_area_alloc_block(PMD_SIZE, flags, node); + if (!p) + return -ENOMEM; + + entry = pfn_pte(__pa(p) >> PAGE_SHIFT, PAGE_KERNEL); + mk_pte_huge(entry); + set_pmd(pmd, __pmd(pte_val(entry))); + } + } + + return 0; +} +#endif Index: linux-2.6/include/asm-x86/pgtable_64.h =================================================================== --- linux-2.6.orig/include/asm-x86/pgtable_64.h 2007-11-15 21:24:47.079904686 -0800 +++ linux-2.6/include/asm-x86/pgtable_64.h 2007-11-15 21:25:18.578584246 -0800 @@ -138,6 +138,7 @@ static inline pte_t ptep_get_and_clear_f #define VMALLOC_START _AC(0xffffc20000000000, UL) #define VMALLOC_END _AC(0xffffe1ffffffffff, UL) #define VMEMMAP_START _AC(0xffffe20000000000, UL) +#define CPU_AREA_BASE _AC(0xfffff20000000000, UL) #define MODULES_VADDR _AC(0xffffffff88000000, UL) #define MODULES_END _AC(0xfffffffffff00000, UL) #define MODULES_LEN (MODULES_END - MODULES_VADDR) Index: linux-2.6/arch/x86/Kconfig =================================================================== --- linux-2.6.orig/arch/x86/Kconfig 2007-11-15 21:24:47.075904383 -0800 +++ linux-2.6/arch/x86/Kconfig 2007-11-15 21:25:18.578584246 -0800 @@ -163,6 +163,21 @@ config X86_TRAMPOLINE config KTIME_SCALAR def_bool X86_32 + +config CPU_AREA_VIRTUAL + bool + default y + +config CPU_AREA_ORDER + int + default "16" if X86_64 + default "6" if X86_32 + +config CPU_AREA_ALLOC_ORDER + int + default "9" if NUMA && X86_64 + default "0" if !NUMA || X86_32 + source "init/Kconfig" menu "Processor type and features" Index: linux-2.6/arch/x86/mm/init_32.c =================================================================== --- linux-2.6.orig/arch/x86/mm/init_32.c 2007-11-15 21:24:47.067904108 -0800 +++ linux-2.6/arch/x86/mm/init_32.c 2007-11-15 21:25:18.578584246 -0800 @@ -674,6 +674,7 @@ void __init mem_init(void) #if 1 /* double-sanity-check paranoia */ printk("virtual kernel memory layout:\n" " fixmap : 0x%08lx - 0x%08lx (%4ld kB)\n" + " cpu area: 0x%08lx - 0x%08lx (%4ld kb)\n" #ifdef CONFIG_HIGHMEM " pkmap : 0x%08lx - 0x%08lx (%4ld kB)\n" #endif @@ -684,6 +685,8 @@ void __init mem_init(void) " .text : 0x%08lx - 0x%08lx (%4ld kB)\n", FIXADDR_START, FIXADDR_TOP, (FIXADDR_TOP - FIXADDR_START) >> 10, + CPU_AREA_BASE, FIXADDR_START, + (FIXADDR_START - CPU_AREA_BASE) >> 10, #ifdef CONFIG_HIGHMEM PKMAP_BASE, PKMAP_BASE+LAST_PKMAP*PAGE_SIZE, Index: linux-2.6/include/asm-x86/pgtable_32.h =================================================================== --- linux-2.6.orig/include/asm-x86/pgtable_32.h 2007-11-15 21:24:47.087904440 -0800 +++ linux-2.6/include/asm-x86/pgtable_32.h 2007-11-15 21:25:18.578584246 -0800 @@ -79,11 +79,14 @@ void paging_init(void); #define VMALLOC_START (((unsigned long) high_memory + \ 2*VMALLOC_OFFSET-1) & ~(VMALLOC_OFFSET-1)) #ifdef CONFIG_HIGHMEM -# define VMALLOC_END (PKMAP_BASE-2*PAGE_SIZE) +# define CPU_AREA_BASE (PKMAP_BASE - NR_CPUS * \ + (1 << (CONFIG_CPU_AREA_ORDER + PAGE_SHIFT))) #else -# define VMALLOC_END (FIXADDR_START-2*PAGE_SIZE) +# define CPU_AREA_BASE (FIXADDR_START - NR_CPUS * \ + (1 << (CONFIG_CPU_AREA_ORDER + PAGE_SHIFT))) #endif +#define VMALLOC_END (CPU_AREA_BASE - 2 * PAGE_SIZE) /* * _PAGE_PSE set in the page directory entry just means that * the page directory entry points directly to a 4MB-aligned block of -- - 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/