linux-kernel - Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

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: <1ddf01c827d6$40106500$0a01a8c0@robmhp>
Date:	Fri, 16 Nov 2007 09:24:06 +1100
From:	"Rob Mueller" <robm@...tmail.fm>
To:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>
Cc:	"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>,
	"riel" <riel@...hat.com>, "Anton Altaparmakov" <aia21@....ac.uk>
Subject: Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)


> That's my personal opinion, and I realize that some of the commercial
> vendors may care about their insane customers' satisfaction, but I'm
> simply not interested in insane users. If they have that much RAM (and
> bought it a few years ago when a 64-bit CPU wasn't an option), they can't
> be poor.

>From our perspective, the main issue is that some of these machines we spent 
quite a bit of money on the big RAM (for it's day) + lots of 15k RPM SCSI 
drives + multi-year support contracts. They're highly IO bound, and barely 
use 10-20% of their old 2.4Ghz Prestonia Xeon CPUs. It's hard to justify 
junking those machines < 5 years.

We have a couple of 6G machines and some 8G machines using PAE. On the 
whole, they actually have been working really well (hmmm, apart from the 
recent dirty pages issue + reiserfs data=journal leaks + inodes in lowmem 
limits)

Rob

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