DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=EucXKG+SoWsWBzZqNGY4/FNdCSyYBt18wYD/+VjthzXr3by7ktGgx0IoROTS9Zu71G1mqFQEc5Hpab5v+k4IVpG3fStgeDupi+Pv7GiUhynhGuOS+56lgdhb8Y5YIyYbDQ2zWk0jQYZMd9dGOGmzwV+m92hOmpe4KOmgnmc1wS0=
Message-ID: <12c511ca0603012015g7a5bfa8dw4295c59f5dace4f9@mail.gmail.com>
Date: Wed, 1 Mar 2006 20:15:12 -0800
From: "Tony Luck" <tony.luck@intel.com>
To: "Zou Nan hai" <nanhai.zou@intel.com>
Subject: Re: [Patch] Move swiotlb_init early on X86_64
Cc: LKML <linux-kernel@vger.kernel.org>, "Andrew Morton" <akpm@osdl.org>,
       "Andi Kleen" <ak@suse.de>,
       "Venkatesh Pallipadi" <venkatesh.pallipadi@intel.com>
In-Reply-To: <1141175458.2642.78.camel@linux-znh>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <1141175458.2642.78.camel@linux-znh>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 796
Lines: 20

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.

-Tony
-
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/