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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46A87858.40005@garzik.org>
Date:	Thu, 26 Jul 2007 06:32:56 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Alex Tomas <alex@...sterfs.com>
CC:	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

Alex Tomas wrote:
> Good day,
> 
> please review ...
> 
> thanks, Alex
> 
> 
> basic delayed allocation in VFS:
> 
>  * block_prepare_write() can be passed special ->get_block() which
>    doesn't allocate blocks, but reserve them and mark bh delayed
>  * a filesystem can use mpage_da_writepages() with other ->get_block()
>    which doesn't defer allocation. mpage_da_writepages() finds all
>    non-allocated blocks and try to allocate them with minimal calls
>    to ->get_block(), then submit IO using __mpage_writepage()
> 
> 
> Signed-off-by: Alex Tomas <alex@...sterfs.com>

Is this based on Christoph's work?

Christoph, or some other XFS hacker, already did generic delalloc, 
modeled on the XFS delalloc code.

	Jeff


-
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