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: <alpine.LFD.0.9999.0711151426280.4260@woody.linux-foundation.org>
Date:	Thu, 15 Nov 2007 14:31:02 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Chris Friesen <cfriesen@...tel.com>
cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Bron Gondwana <brong@...tmail.fm>,
	Christian Kujau <lists@...dbynature.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	robm@...tmail.fm, riel <riel@...hat.com>,
	Anton Altaparmakov <aia21@....ac.uk>
Subject: Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel
 Bugs)



On Thu, 15 Nov 2007, Chris Friesen wrote:
> 
> We've got some 32-bit 8GB boxes for which both of these would hold true.

Still not enough of a reason for me to care.

Remember - I'm the guy who refused to merge RH's 4G:4G patches because I 
thought they were an unsupportable nightmare.

I care a lot about future supportability, and HIGHMEM is there purely as a 
temporary wart and blip on the screen.

I did acknowledge that others may care more, but the fact is, I suspect 
that it's going to be cheaper to literally buy and ship a new machine to a 
customer than to really "suppport" it in any other form.

Side note: HIGHMEM64G works perfectly fine with 12GB of RAM under 
*limited*loads*. If your customer does certain well-defined and simple 
things that don't put huge and varied loads on the VFS or VM layer, then 
12GB+ is probably fine regardless.

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