lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 06 Apr 2010 16:32:00 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Youngwhan Song <breadncup@...il.com>
CC:	Venkatram Tummala <venkatram867@...il.com>,
	Joel Fernandes <agnel.joel@...il.com>,
	Frank Hu <frank.hu.2001@...il.com>,
	hayfeng Lee <teklife.kernel@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-kernel@...kernel.org" <linux-kernel@...kernel.org>,
	"kernelnewbies@...linux.org" <kernelnewbies@...linux.org>
Subject: Re: why choose 896MB to the start point of ZONE_HIGHMEM

On 04/06/2010 04:27 PM, Youngwhan Song wrote:
> Nice explanation, Venkatram,
> 
> Just one question pop up mind.
> 
> What if actual physical memory is only 256MB? How does kernel divide
> virtual memory? Do we need to specify the region to kernel? Or will
> kernel itself decide it automatically? 
> 

If there is less than 896 MB of physical memory, the vmalloc region is
automatically extended (in your case, it will be 768 MB in size.)  There
will be no HIGHMEM in such a case, and if you are compiling your own
kernel you will gain considerable speed by disabling HIGHMEM support
completely.

This, of course, was the norm back when Linux was first created, and a
typical amount of memory was 8 MB or so.  That we'd have gigabytes of
memory seemed very distant at the time.

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ