linux-ext4 - Re: [RFC] basic delayed allocation in VFS

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]

Date:	Fri, 27 Jul 2007 16:42:57 +0400
From:	Alex Tomas <alex@...sterfs.com>
To:	Jeff Garzik <jeff@...zik.org>
CC:	David Chinner <dgc@....com>,
	ext4 development <linux-ext4@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: [RFC] basic delayed allocation in VFS

Jeff Garzik wrote:
> Alex Tomas wrote:
>>> So without the ability to attach specific I/O completions to bios
>>> or support for unwritten extents directly in __mpage_writepage,
>>> there is no way XFS can use this "generic" delayed allocation code.
>>
>> I didn't say "generic", see Subject: :)
> 
> Well, it shouldn't even be in the VFS layer if it's only usable by one 
> filesystem.

sorry, but it seems I can say the same about iomap/ioend. I think
mpage_da_writepages() is simple enough to be adopted by other
filesystem, ext2 for example.

thanks, Alex

-
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