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
| ||
|
Date: Tue, 29 Jan 2008 00:29:28 -0800 (PST) From: david@...g.hm To: Theodore Tso <tytso@....EDU> cc: Pavel Machek <pavel@....cz>, Valdis.Kletnieks@...edu, David Chinner <dgc@....com>, Valerie Henson <val@...consulting.com>, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, Andreas Dilger <adilger@...sterfs.com>, Ric Wheeler <ric@....com> Subject: Re: [RFC] Parallelize IO for e2fsck On Mon, 28 Jan 2008, Theodore Tso wrote: > On Mon, Jan 28, 2008 at 07:30:05PM +0000, Pavel Machek wrote: >> >> As user pages are always in highmem, this should be easy to decide: >> only send SIGDANGER when highmem is full. (Yes, there are >> inodes/dentries/file descriptors in lowmem, but I doubt apps will >> respond to SIGDANGER by closing files). > > Good point; for a system with at least (say) 2GB of memory, that > definitely makes sense. For a system with less than 768 megs of > memory (how quaint, but it wasn't that long ago this was a lot of > memory :-), there wouldn't *be* any memory in highmem at all.... not to mention machines with 1G of ram (900M lowmem, 128M highmem) David Lang - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists