From: Andi Kleen <ak@suse.de>
To: "Tony Luck" <tony.luck@intel.com>
Cc: "Zou Nan hai" <nanhai.zou@intel.com>,
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: Thu, 2 Mar 2006 05:30:08 +0100 [thread overview]
Message-ID: <200603020530.09552.ak@suse.de> (raw)
In-Reply-To: <12c511ca0603012015g7a5bfa8dw4295c59f5dace4f9@mail.gmail.com>
On Thursday 02 March 2006 05:15, Tony Luck wrote:
> On 01 Mar 2006 09:10:58 +0800, Zou Nan hai <nanhai.zou@intel.com> 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.
>
> Shouldn't memmap be allocated from memory above 4G (if available)? Using
> up lots of <4G memory on something that doesn't need to be below 4G
> sounds like a poor use of resources.
On the really large machines it will be distributed over the nodes anyways.
But yes the single node SMP case should probably allocate it higher.
-Andi
next prev parent reply other threads:[~2006-03-02 4:30 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 [this message]
2006-03-02 4:33 ` Zou Nan hai
2006-03-07 8:39 ` Andi Kleen
2006-03-07 23:23 ` Zou Nan hai
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=200603020530.09552.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=tony.luck@intel.com \
--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