linux-ext4 - Re: [RFC] delayed allocation for ext4

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: <m37iwbqozt.fsf@bzzz.home.net>
Date:	Fri, 29 Dec 2006 07:56:22 +0300
From:	Alex Tomas <alex@...sterfs.com>
To:	David Chinner <dgc@....com>
Cc:	Alex Tomas <alex@...sterfs.com>, linux-ext4@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] delayed allocation for ext4

>>>>> David Chinner (DC) writes:

 DC> So that mean's we'll have 2 separate mechanisms for marking
 DC> pages as delalloc. XFS uses the BH_delay flag to indicate
 DC> that a buffer (block) attached to the page is using delalloc.
 >> 
 >> well, for blocksize=pagesize we can save 56 bytes on every page.

 DC> Sure, but it means that ext4 w/ delalloc won't work on lots of
 DC> machines....

it does not currenly. but I'm going to implement that. not sure
whether it's worth to have two different codepaths for
block size=page size and block size < page size.

 DC> FWIW, how does this mechanism deal with block size < page size?
 DC> Don't you have to track delalloc on a block basis rather than
 DC> a page basis?
 >> 
 >> I'm still thinking how better to deal with that w/o much code duplication.

 DC> Code duplication in ext4, or across all filesystems?

given what Andrew said about moving the code into VFS, it's more
about all filesystems.

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