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: Sat, 30 Jun 2007 11:44:08 +0100 From: Christoph Hellwig <hch@...radead.org> To: Chris Mason <chris.mason@...cle.com> Cc: Nick Piggin <nickpiggin@...oo.com.au>, Nick Piggin <npiggin@...e.de>, Jeff Garzik <jeff@...zik.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Memory Management List <linux-mm@...ck.org>, linux-fsdevel@...r.kernel.org Subject: Re: [RFC] fsblock On Mon, Jun 25, 2007 at 08:25:21AM -0400, Chris Mason wrote: > > write_begin/write_end is a step in that direction (and it helps > > OCFS and GFS quite a bit). I think there is also not much reason > > for writepage sites to require the page to lock the page and clear > > the dirty bit themselves (which has seems ugly to me). > > If we keep the page mapping information with the page all the time (ie > writepage doesn't have to call get_block ever), it may be possible to > avoid sending down a locked page. But, I don't know the delayed > allocation internals well enough to say for sure if that is true. The point of delayed allocations is that the mapping information doesn't even exist until writepage for new allocations :) - 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