ext4: optimize starting extent in ext4_ext_rm_leaf()
authorAshish Sangwan <a.sangwan@samsung.com>
Mon, 1 Jul 2013 12:12:41 +0000 (08:12 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Mon, 1 Jul 2013 12:12:41 +0000 (08:12 -0400)
commit6ae06ff51eab5dcbbf959b05ce0f11003a305ba5
tree0205ef491e599b188fc653872c166db57ae3b482
parent41a5b913197c3a25fddef1735dc9b3d1fdc57428
ext4: optimize starting extent in ext4_ext_rm_leaf()

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@samsung.com>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
fs/ext4/extents.c