From: Zou Nan hai <nanhai.zou@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: [Patch] Move swiotlb_init early on X86_64
Date: 08 Mar 2006 07:23:08 +0800 [thread overview]
Message-ID: <1141773788.2537.27.camel@linux-znh> (raw)
In-Reply-To: <200603070939.03368.ak@suse.de>
On Tue, 2006-03-07 at 16:39, Andi Kleen wrote:
> On Wednesday 01 March 2006 02:10, Zou Nan hai wrote:
> > on X86_64, swiotlb buffer is allocated in mem_init, after memmap and vfs cache allocation.
> >
> > On platforms with huge physical memory,
> > large memmap and vfs cache may eat up all usable system memory
> > under 4G.
> >
> > Move swiotlb_init early before memmap is allocated can
> > solve this issue.
> >
> > Signed-off-by: Zou Nan hai <Nanhai.zou@intel.com>
>
>
> I came up with a simpler change now that should fix the problem too.
> It just try to move the memmap to the end of the node. I don't have a system
> big enough to test the original problem though.
>
> It should be fairly safe because if the allocation fails we just fallback
> to the normal old way of allocating it near the beginning.
>
> Try to allocate node memmap near the end of node
>
> This fixes problems with very large nodes (over 128GB) filling up all of
> the first 4GB with their mem_map and not leaving enough
> space for the swiotlb.
>
>
> Signed-off-by: Andi Kleen <ak@suse.de>
>
> ---
> arch/x86_64/mm/numa.c | 12 +++++++++++-
> include/linux/bootmem.h | 3 +++
> mm/bootmem.c | 2 +-
> 3 files changed, 15 insertions(+), 2 deletions(-)
>
> Index: linux/arch/x86_64/mm/numa.c
> ===================================================================
> --- linux.orig/arch/x86_64/mm/numa.c
> +++ linux/arch/x86_64/mm/numa.c
> @@ -172,7 +172,7 @@ void __init setup_node_bootmem(int nodei
> /* Initialize final allocator for a zone */
> void __init setup_node_zones(int nodeid)
> {
> - unsigned long start_pfn, end_pfn;
> + unsigned long start_pfn, end_pfn, memmapsize, limit;
> unsigned long zones[MAX_NR_ZONES];
> unsigned long holes[MAX_NR_ZONES];
>
> @@ -182,6 +182,16 @@ void __init setup_node_zones(int nodeid)
> Dprintk(KERN_INFO "Setting up node %d %lx-%lx\n",
> nodeid, start_pfn, end_pfn);
>
> + /* Try to allocate mem_map at end to not fill up precious <4GB
> + memory. */
> + memmapsize = sizeof(struct page) * (end_pfn-start_pfn);
> + limit = end_pfn << PAGE_SHIFT;
> + NODE_DATA(nodeid)->node_mem_map =
> + __alloc_bootmem_core(NODE_DATA(nodeid)->bdata,
> + memmapsize, SMP_CACHE_BYTES,
> + limit,
> + round_down(limit - memmapsize, PAGE_SIZE));
> +
, round_down(limit - memmapsize, PAGE_SIZE), limit);?
Zou Nan hai
next prev parent reply other threads:[~2006-03-08 1:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 1:10 [Patch] Move swiotlb_init early on X86_64 Zou Nan hai
2006-03-02 4:15 ` Tony Luck
2006-03-02 4:30 ` Andi Kleen
2006-03-02 4:33 ` Zou Nan hai
2006-03-07 8:39 ` Andi Kleen
2006-03-07 23:23 ` Zou Nan hai [this message]
2006-03-08 9:33 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-03-02 9:09 Zhang, Yanmin
2006-03-02 23:35 ` Zou Nan hai
2006-03-03 1:32 ` Andi Kleen
2006-03-03 1:59 Pallipadi, Venkatesh
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=1141773788.2537.27.camel@linux-znh \
--to=nanhai.zou@intel.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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