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: Wed, 11 May 2011 01:28:32 +0900 From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> To: Jan Kara <jack@...e.cz> Cc: "Darrick J. Wong" <djwong@...ibm.com>, Theodore Tso <tytso@....edu>, Alexander Viro <viro@...iv.linux.org.uk>, Jens Axboe <axboe@...nel.dk>, "Martin K. Petersen" <martin.petersen@...cle.com>, Jeff Layton <jlayton@...hat.com>, Dave Chinner <david@...morbit.com>, linux-kernel <linux-kernel@...r.kernel.org>, Dave Hansen <dave@...ux.vnet.ibm.com>, Christoph Hellwig <hch@...radead.org>, linux-mm@...ck.org, Chris Mason <chris.mason@...cle.com>, Joel Becker <jlbec@...lplan.org>, linux-scsi <linux-scsi@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-ext4@...r.kernel.org, Mingming Cao <mcao@...ibm.com> Subject: Re: [PATCHSET v3.1 0/7] data integrity: Stabilize pages during writeback for various fses Jan Kara <jack@...e.cz> writes: >> Maybe possible, but you really think on usual case just blocking is >> better? > Define usual case... As Christoph noted, we don't currently have a real > practical case where blocking would matter (since frequent rewrites are > rather rare). So defining what is usual when we don't have a single real > case is kind of tough ;) OK. E.g. usual workload on desktop, but FS like ext2/fat. -- OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> -- 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