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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 18, 2013 at 9:10 PM, Theodore Ts'o <tytso@xxxxxxx> wrote:
> On Fri, May 24, 2013 at 08:09:17PM +0530, ashishsangwan2@xxxxxxxxx wrote:
>> From: Ashish Sangwan <a.sangwan@xxxxxxxxxxx>
>>
>> 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@xxxxxxxxxxx>
>> Signed-off-by: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
>
> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux