linux-kernel - Re: why choose 896MB to the start point of ZONE

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 06 Apr 2010 13:18:51 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Frank Hu <frank.hu.2001@...il.com>
CC:	Joel Fernandes <agnel.joel@...il.com>,
	hayfeng Lee <teklife.kernel@...il.com>,
	linux-kernel@...r.kernel.org, linux-kernel@...kernel.org,
	kernelnewbies@...linux.org
Subject: Re: why choose 896MB to the start point of ZONE_HIGHMEM

On 04/06/2010 01:15 PM, Frank Hu wrote:
> 
> thought that you can only configure how to split the VM like 1G/3G or
> 2G/2G. But the DMA zone size, the 128MB space for I/O is not
> configurable. The NORMAL zone size will be deducted based on the VM
> Split and some hard coded DMA zone and 128 MB space size.
> 
> I am not a guru in this space... so I might be wrong.

And you are.  The vmalloc zone (not DMA zone -- that's something
entirely different) is configurable via the vmalloc= kernel command line
option.

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