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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46366B34.3050003@gmail.com>
Date:	Mon, 30 Apr 2007 23:18:28 +0100
From:	Matt Keenan <tank.en.mate@...il.com>
To:	William Lee Irwin III <wli@...omorphy.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Bradley Chapman <kakadu@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: CONFIG_HIGHMEM4G and 1GB RAM

William Lee Irwin III wrote:
> On Sat, 28 Apr 2007 21:26:42 +0100 "Bradley Chapman" <kakadu@...il.com> wrote:
>   
>>> Basically, all I want to know is whether or not enabling
>>> CONFIG_HIGHMEM4G for a laptop that has exactly 1GB of RAM will result
>>> in any performance degradation.
>>>       
>
> On Mon, Apr 30, 2007 at 12:17:55AM -0700, Andrew Morton wrote:
>   
>> I would expect the advantages of the additional 128MB to considerably
>> outweigh the cost of turning on CONFIG_HIGHMEM4G.
>> That cost will be a little extra CPU consumption inside the kernel, but the
>> great majority of CPU consumption usually happens in userspace anyway.
>>     
>
> The CONFIG_VMSPLIT config options were merged for such cases.
>
> It should be able to split on any 4MB-aligned boundary in
> CONFIG_HIGHMEM4G. CONFIG_VMSPLIT_3G_OPT appears to do something of
> this sort to use an entire 1GB RAM with minimal user address space
> reduction.
>
> This is an ELF ABI violation but the number of major applications
> that break is apparently low.
>
>   
wine and some java implementations being two of the big caveats.

Matt

-
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