Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752675Ab0DHCX0 (ORCPT ); Wed, 7 Apr 2010 22:23:26 -0400 Received: from mail-vw0-f46.google.com ([209.85.212.46]:65052 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775Ab0DHCXX convert rfc822-to-8bit (ORCPT ); Wed, 7 Apr 2010 22:23:23 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Xtj/IxoSdppxXwjC2zOg9kByn+KmRb1An8R0w2WKciXvWuhPMlpXbpApKRYW1e9eKP UoZg5CbkBlvsTIJ9Ek+Z4nwRcgD57pJmRdTUCMoD3RupiuvnoFAU80EytgWbVmpqM+nU O+t0p64ng3UTjDRKDK/0vWnPIYVX38XtFBlgI= MIME-Version: 1.0 In-Reply-To: <4BBCBD8B.6070701@zytor.com> References: <4BBBC470.4050002@zytor.com> <4BBBE976.1000603@zytor.com> <4BBCBD8B.6070701@zytor.com> Date: Thu, 8 Apr 2010 07:53:21 +0530 Message-ID: Subject: Re: why choose 896MB to the start point of ZONE_HIGHMEM From: Nobin Mathew To: "H. Peter Anvin" Cc: Himanshu Aggarwal , Chetan Nanda , Xianghua Xiao , Venkatram Tummala , Youngwhan Song , Joel Fernandes , Frank Hu , hayfeng Lee , "linux-kernel@vger.kernel.org" , "linux-kernel@zh-kernel.org" , "kernelnewbies@nl.linux.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1610 Lines: 45 On Wed, Apr 7, 2010 at 10:44 PM, H. Peter Anvin wrote: > On 04/07/2010 09:48 AM, Himanshu Aggarwal wrote: >> I think for some architectures, the position of highmem is constrained >> by hardware as well. ?It is not always a kernel decision and not always >> configurable as in case of x86. > > > This is correct. > >> In case of MIPS32, low memory is between 0 and 512 MB and high memory >> starts above 512 MB. Also the user space is of size 2 GB. >> >> Please see the definition of macros PAGE_OFFSET and HIGHMEM_START at : >> http://lxr.linux.no/linux+v2.6.33/arch/mips/include/asm/mach-generic/spaces.h > > Right so far... > >> This is because MIPS32 processors have KSEG0 and KSEG1 segments lying >> between 0 and 512 MB and KSEG2/3 lies above it. >> >> May be someone on the group can confirm this. > > Wrong. ?I have to say this thread has been just astonishing in the > amount of misinformation. > > On MIPS32, userspace is 0-2 GB, kseg0 is 2.0-2.5 GB and kseg1 is 2.5-3.0 > GB. ?kseg2/3 (3.0-4.0 GB), which invokes the TLB, is used for the > vmalloc/iomap/kmap area. > > LOWMEM has to fit inside kseg0, so LOWMEM is limited to 512 MB in thie > current Linux implementation. http://www.johnloomis.org/microchip/pic32/memory/memory.html So what is the memory division here in mips, again 1:3? kseg2 is already 1 GB address space? -Nobin -- 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/