linux-ext4 - Re: [PATCH] ext4: optimize extent selection for block removal in case of hole punch

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 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:	Wed, 19 Jun 2013 19:15:35 +0530
From:	Ashish Sangwan <ashishsangwan2@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	adilger@...ger.ca, ext4 development <linux-ext4@...r.kernel.org>,
	Ashish Sangwan <a.sangwan@...sung.com>,
	Namjae Jeon <namjae.jeon@...sung.com>
Subject: Re: [PATCH] ext4: optimize extent selection for block removal in case
 of hole punch

On Tue, Jun 18, 2013 at 9:10 PM, Theodore Ts'o <tytso@....edu> wrote:
> On Fri, May 24, 2013 at 08:09:17PM +0530, ashishsangwan2@...il.com wrote:
>> From: Ashish Sangwan <a.sangwan@...sung.com>
>>
>> Both hole punch and truncate use ext4_ext_rm_leaf for removing
>> blocks. Currently we choose the last extent as the starting
>> point for removing blocks: ex = EXT_LAST_EXTENT(eh);
>> This is OK for truncate but for hole punch we can optimize the
>> extent selection as the path is already initialized.
>> We could use this information to select proper starting extent.
>> The code change in this patch will not affect truncate as for
>> truncate path[depth].p_ext will always be NULL.
>>
>> Signed-off-by: Ashish Sangwan <a.sangwan@...sung.com>
>> Signed-off-by: Namjae Jeon <namjae.jeon@...sung.com>
>
> Applied, thanks.
Hi Ted,

Sorry I cannot see the patch changes in ext4 dev branch.

Regards,
Ashish
>
>                                         - Ted
--
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