Message-ID: <4848F233.10008@goop.org>
Date: Fri, 06 Jun 2008 09:15:47 +0100
From: Jeremy Fitzhardinge <jeremy@goop.org>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Jan Beulich <jbeulich@novell.com>
CC: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
       Stable Kernel <stable@kernel.org>, x86@kernel.org,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: set PAE PHYSICAL_MASK_SHIFT to match 64-bit
References: <4848046A.5060006@goop.org> <87ve0ntk6v.fsf@basil.nowhere.org> <4848EE5C.6040003@goop.org> <48490DEC.76E4.0078.0@novell.com>
In-Reply-To: <48490DEC.76E4.0078.0@novell.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1357
Lines: 37

Jan Beulich wrote:
>>>> Jeremy Fitzhardinge <jeremy@goop.org> 06.06.08 09:59 >>>
>>>>         
>> Andi Kleen wrote:
>>     
>>> Jeremy Fitzhardinge <jeremy@goop.org> writes:
>>>   
>>>       
>>>> The 46-bit mask used in 64-bit seems pretty arbitrary. 
>>>>     
>>>>         
>>> The rationale for the 46 bits is that the kernel needs roughly 4x as 
>>> much virtual space as physical space and the virtual space is limited
>>> to 48bits.
>>>
>>> To be exact 47 bits is always user space and the 47 bits remaining
>>> for the kernel are split into half, with one half for the direct mapping
>>> and the other half for random mappings.  With some pushing you could
>>> extend it to 46.5 bits or so, but beyond that you'll be in trouble.
>>>   
>>>       
>> Why's that?  Is the issue the amount of memory needed for pagetables and 
>> page structures if you did have more than 2^48 bytes of physical memory?
>>     
>
> No, it's the fact that the 1:1 mapping needs as much virtual space as
> the physical range covered (including all holes).

Right, I see.  And suddenly 64-bits seems... constrained. ;)

    J

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