| Message ID | 20200325093728.204211-2-harshadshirwadkar@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | [1/2] ext4: return lblk from ext4_find_entry | expand |
On Mar 25, 2020, at 3:37 AM, Harshad Shirwadkar <harshadshirwadkar@gmail.com> wrote: > But note that most of the shrinking happens during last 1-2% deletions > in an average case. Therefore, the next step here is to merge dx nodes > when possible. That can be achieved by storing the fullness index in > htree nodes. But that's an on-disk format change. We can instead build > on tooling added by this patch to perform reverse lookup on a dx > node and then reading adjacent nodes to check their fullness. Thank you for updating these patches again. I haven't had a chance to look at them yet, but I hope to review the patches in the near future. As for storing the fullness on disk changing the on-disk format... That is true, but the original htree implementation anticipated this and reserved space in the htree index to store the fullness, so it would not break the ability of older kernels to access directories with the fullness information. I think if you used just a few bits (maybe just 2) to store: 0 = unset (every directory today) 1 = under 20% full 2 = under 40% full 3 = under 60% full or similar. It doesn't matter if they are more full since they won't be candidates for merging, and then lazily update the htree index fullness as entries are removed, this will simplify the shrinking process, and will avoid the need to repeatedly scan the leaf blocks to see if they are empty enough for merging. It wouldn't be any worse *not* to store these values on disk after the first time a "0 = unset" entry was found and not merged, or setting the fullness on the merged block if it is merged, and running "e2fsck -D" can easily update the fullness values. The benefit of using 20%, 40%, and 60% as the fullness markers is that it is possible to either merge adjacent 60% and 40% blocks or alternately a 60% and two adjacent 20% blocks. Also, since these values are very coarse they would not need to be updated frequently. If the values are slightly outdated, then it is again not worse than the "always scan" model (one scan and the fullness would be updated), but more efficient than repeat scanning. Using only two bits for fullness also leaves two bits free for future use. Cheers, Andreas
On Wed, Mar 25, 2020 at 3:06 AM Andreas Dilger <adilger@dilger.ca> wrote: > > On Mar 25, 2020, at 3:37 AM, Harshad Shirwadkar <harshadshirwadkar@gmail.com> wrote: > > But note that most of the shrinking happens during last 1-2% deletions > > in an average case. Therefore, the next step here is to merge dx nodes > > when possible. That can be achieved by storing the fullness index in > > htree nodes. But that's an on-disk format change. We can instead build > > on tooling added by this patch to perform reverse lookup on a dx > > node and then reading adjacent nodes to check their fullness. > > Thank you for updating these patches again. I haven't had a chance to look > at them yet, but I hope to review the patches in the near future. > > As for storing the fullness on disk changing the on-disk format... That is > true, but the original htree implementation anticipated this and reserved > space in the htree index to store the fullness, so it would not break the > ability of older kernels to access directories with the fullness information. > Yeah, you are right, good to know that we have bits reserved already and that wouldn't break older kernels if we use these in future. > I think if you used just a few bits (maybe just 2) to store: > 0 = unset (every directory today) > 1 = under 20% full > 2 = under 40% full > 3 = under 60% full > > or similar. It doesn't matter if they are more full since they won't be > candidates for merging, and then lazily update the htree index fullness > as entries are removed, this will simplify the shrinking process, and will > avoid the need to repeatedly scan the leaf blocks to see if they are empty > enough for merging. It wouldn't be any worse *not* to store these values > on disk after the first time a "0 = unset" entry was found and not merged, > or setting the fullness on the merged block if it is merged, and running > "e2fsck -D" can easily update the fullness values. > > The benefit of using 20%, 40%, and 60% as the fullness markers is that it > is possible to either merge adjacent 60% and 40% blocks or alternately a > 60% and two adjacent 20% blocks. Also, since these values are very coarse > they would not need to be updated frequently. If the values are slightly > outdated, then it is again not worse than the "always scan" model (one scan > and the fullness would be updated), but more efficient than repeat scanning. > > Using only two bits for fullness also leaves two bits free for future use. Thanks Andreas, that makes sense. This kind of merging will require lot of tooling provided in this patch - for example swapping out freed block with last block to not leave any holes. So, my hope is that we get this patch in first and thereby get a step closer to coalescing solution. Thanks, Harshad > > Cheers, Andreas > > > > >
On Mar 26, 2020, at 1:49 PM, harshad shirwadkar <harshadshirwadkar@gmail.com> wrote: > > On Wed, Mar 25, 2020 at 3:06 AM Andreas Dilger <adilger@dilger.ca> wrote: >> >> On Mar 25, 2020, at 3:37 AM, Harshad Shirwadkar <harshadshirwadkar@gmail.com> wrote: >>> But note that most of the shrinking happens during last 1-2% deletions >>> in an average case. Therefore, the next step here is to merge dx nodes >>> when possible. That can be achieved by storing the fullness index in >>> htree nodes. But that's an on-disk format change. We can instead build >>> on tooling added by this patch to perform reverse lookup on a dx >>> node and then reading adjacent nodes to check their fullness. >> >> Thank you for updating these patches again. I haven't had a chance to look >> at them yet, but I hope to review the patches in the near future. >> >> As for storing the fullness on disk changing the on-disk format... That is >> true, but the original htree implementation anticipated this and reserved >> space in the htree index to store the fullness, so it would not break the >> ability of older kernels to access directories with the fullness information. >> > Yeah, you are right, good to know that we have bits reserved already > and that wouldn't break older kernels if we use these in future. >> I think if you used just a few bits (maybe just 2) to store: >> 0 = unset (every directory today) >> 1 = under 20% full >> 2 = under 40% full >> 3 = under 60% full >> >> or similar. It doesn't matter if they are more full since they won't be >> candidates for merging, and then lazily update the htree index fullness >> as entries are removed, this will simplify the shrinking process, and will >> avoid the need to repeatedly scan the leaf blocks to see if they are empty >> enough for merging. It wouldn't be any worse *not* to store these values >> on disk after the first time a "0 = unset" entry was found and not merged, >> or setting the fullness on the merged block if it is merged, and running >> "e2fsck -D" can easily update the fullness values. >> >> The benefit of using 20%, 40%, and 60% as the fullness markers is that it >> is possible to either merge adjacent 60% and 40% blocks or alternately a >> 60% and two adjacent 20% blocks. Also, since these values are very coarse >> they would not need to be updated frequently. If the values are slightly >> outdated, then it is again not worse than the "always scan" model (one scan >> and the fullness would be updated), but more efficient than repeat scanning. >> >> Using only two bits for fullness also leaves two bits free for future use. > > Thanks Andreas, that makes sense. This kind of merging will require > lot of tooling provided in this patch - for example swapping out freed > block with last block to not leave any holes. So, my hope is that we > get this patch in first and thereby get a step closer to coalescing > solution. Definitely I *do not* want to block the landing of these initial patches until a "full featured" directory shrinking is complete. These patches at least provide some basic functionality, and will at least shrink a large directory if it becomes totally empty so I'm in favour of that. Cheers, Andreas
On Mar 25, 2020, at 3:37 AM, Harshad Shirwadkar <harshadshirwadkar@gmail.com> wrote: > > This patch adds shrinking support for htree based directories. The > high level algorithm is as follows: > > * If after dentry removal the dirent block (let's call it B) becomes > empty, then remove its references in its dx parent. > * Swap its contents with that of the last block (L) in directory. > * Update L's parents to point to B instead. > * Remove L > * Repeat this for all the ancestors of B. > > We add variants of dx_probe that allow us perform reverse lookups from > a logical block to its dx parents. > > Ran kvm-xfstests smoke and verified that no new failures are > introduced. Ran shrinking for directories with following number of > files and then deleted files one by one: > * 1000 (size before deletion 36K, after deletion 4K) > * 10000 (size before deletion 196K, after deletion 4K) > * 100000 (size before deletion 2.1M, after deletion 4K) > * 200000 (size before deletion 4.2M, after deletion 4K) > > In all cases directory shrunk significantly. We fallback to linear > directories if the directory becomes empty. > > But note that most of the shrinking happens during last 1-2% deletions > in an average case. Therefore, the next step here is to merge dx nodes > when possible. That can be achieved by storing the fullness index in > htree nodes. But that's an on-disk format change. We can instead build > on tooling added by this patch to perform reverse lookup on a dx > node and then reading adjacent nodes to check their fullness. > > This patch supersedes the other directory shrinking patch sent in Aug > 2019 ("ext4: attempt to shrink directory on dentry removal"). > > Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com> > --- > fs/ext4/ext4_jbd2.h | 7 + > fs/ext4/namei.c | 355 ++++++++++++++++++++++++++++++++++++++++++-- > 2 files changed, 353 insertions(+), 9 deletions(-) > > diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c > index d567b9589875..b78c6f9a6eba 100644 > --- a/fs/ext4/namei.c > +++ b/fs/ext4/namei.c > > +/* > + * dx_probe with relaxed checks. This function is used in the directory > + * shrinking code since we can run into intermediate states where we have > + * internal dx nodes with count = 0. > + */ > +static inline struct dx_frame * > +dx_probe_relaxed(struct ext4_filename *fname, struct inode *dir, > + struct dx_hash_info *hinfo, struct dx_frame *frame_in) > +{ > + return __dx_probe(fname, dir, hinfo, frame_in, 0, false); > +} > + > +/* > + * Perform only a parttial dx_probe until we find block end_lblk. (typo) "partial" > +static inline struct dx_frame * > +dx_probe_partial(struct ext4_filename *fname, struct inode *dir, > + struct dx_hash_info *hinfo, struct dx_frame *frame_in, > + ext4_lblk_t end_lblk) > +{ > + return __dx_probe(fname, dir, hinfo, frame_in, end_lblk, false); > +} > + [snip] > +/* > + * This function tries to remove the entry of a dirent block (which was just > + * emptied by the caller) from the dx frame. It does so by reducing the count by > + * 1 and left shifting all the entries after the deleted entry. > + */ > +int > +ext4_remove_dx_entry(handle_t *handle, struct inode *dir, > + struct dx_frame *dx_frame) > +{ > + err = ext4_journal_get_write_access(handle, dx_frame->bh); > + if (err) { > + ext4_std_error(dir->i_sb, err); > + return -EINVAL; > + } > + > + for (; i < count - 1; i++) > + entries[i] = entries[i + 1]; It would be more efficient to do this with "memmove()" rather than copying each entry separately. > + /* > + * If i was 0 when we began above loop, we would have overwritten count > + * and limit values since those values live in dx_entry->hash of the > + * first entry. We need to update count but we should set limit as well. > + */ > + dx_set_count(entries, count - 1); > + dx_set_limit(entries, limit); How hard is it to avoid clobbering these fields in the first place? I'm just thinking that "clobber + fixup" is subject to race conditions at various times in the past, and may become an issue in the future (e.g. with parallel directory operations). > static inline bool is_empty_dirent_block(struct inode *dir, > + struct buffer_head *bh) > +{ This should be combined with ext4_empty_dir() to avoid code duplication. > + struct ext4_dir_entry_2 *de = (struct ext4_dir_entry_2 *)bh->b_data; > + int csum_size = 0; > + > + if (ext4_has_metadata_csum(dir->i_sb) && is_dx(dir)) > + csum_size = sizeof(struct ext4_dir_entry_tail); > + > + return ext4_rec_len_from_disk(de->rec_len, dir->i_sb->s_blocksize) == > + dir->i_sb->s_blocksize - csum_size && de->inode == 0; > +} This looks like a low cost way to determine the leaf block is empty, but checking this for every unlink likely has a non-zero cost. > @@ -2530,6 +2864,9 @@ static int ext4_delete_entry(handle_t *handle, > if (unlikely(err)) > goto out; > > + if (is_dx(dir)) > + ext4_try_dir_shrink(handle, dir, lblk, bh); > + > return 0; It would be useful to run a comparison benchmark between the patched ext4 and unpatched when deleting a large number of entries that checks both CPU usage and performance. That will give us an idea of how much this costs to be checked for every entry. Also, rather than calling ext4_try_dir_shrink() and is_empty_dirent_block() for every entry, couldn't this be returned from ext4_generic_delete_entry(), since it has that information already. Cheers, Andreas
Thanks for the review Andreas. On Sat, Mar 28, 2020 at 5:01 PM Andreas Dilger <adilger@dilger.ca> wrote: > > On Mar 25, 2020, at 3:37 AM, Harshad Shirwadkar <harshadshirwadkar@gmail.com> wrote: > > > > This patch adds shrinking support for htree based directories. The > > high level algorithm is as follows: > > > > * If after dentry removal the dirent block (let's call it B) becomes > > empty, then remove its references in its dx parent. > > * Swap its contents with that of the last block (L) in directory. > > * Update L's parents to point to B instead. > > * Remove L > > * Repeat this for all the ancestors of B. > > > > We add variants of dx_probe that allow us perform reverse lookups from > > a logical block to its dx parents. > > > > Ran kvm-xfstests smoke and verified that no new failures are > > introduced. Ran shrinking for directories with following number of > > files and then deleted files one by one: > > * 1000 (size before deletion 36K, after deletion 4K) > > * 10000 (size before deletion 196K, after deletion 4K) > > * 100000 (size before deletion 2.1M, after deletion 4K) > > * 200000 (size before deletion 4.2M, after deletion 4K) > > > > In all cases directory shrunk significantly. We fallback to linear > > directories if the directory becomes empty. > > > > But note that most of the shrinking happens during last 1-2% deletions > > in an average case. Therefore, the next step here is to merge dx nodes > > when possible. That can be achieved by storing the fullness index in > > htree nodes. But that's an on-disk format change. We can instead build > > on tooling added by this patch to perform reverse lookup on a dx > > node and then reading adjacent nodes to check their fullness. > > > > This patch supersedes the other directory shrinking patch sent in Aug > > 2019 ("ext4: attempt to shrink directory on dentry removal"). > > > > Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com> > > --- > > fs/ext4/ext4_jbd2.h | 7 + > > fs/ext4/namei.c | 355 ++++++++++++++++++++++++++++++++++++++++++-- > > 2 files changed, 353 insertions(+), 9 deletions(-) > > > > diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c > > index d567b9589875..b78c6f9a6eba 100644 > > --- a/fs/ext4/namei.c > > +++ b/fs/ext4/namei.c > > > > +/* > > + * dx_probe with relaxed checks. This function is used in the directory > > + * shrinking code since we can run into intermediate states where we have > > + * internal dx nodes with count = 0. > > + */ > > +static inline struct dx_frame * > > +dx_probe_relaxed(struct ext4_filename *fname, struct inode *dir, > > + struct dx_hash_info *hinfo, struct dx_frame *frame_in) > > +{ > > + return __dx_probe(fname, dir, hinfo, frame_in, 0, false); > > +} > > + > > +/* > > + * Perform only a parttial dx_probe until we find block end_lblk. > > (typo) "partial" Ack > > > +static inline struct dx_frame * > > +dx_probe_partial(struct ext4_filename *fname, struct inode *dir, > > + struct dx_hash_info *hinfo, struct dx_frame *frame_in, > > + ext4_lblk_t end_lblk) > > +{ > > + return __dx_probe(fname, dir, hinfo, frame_in, end_lblk, false); > > +} > > + > [snip] Ack > > +/* > > + * This function tries to remove the entry of a dirent block (which was just > > + * emptied by the caller) from the dx frame. It does so by reducing the count by > > + * 1 and left shifting all the entries after the deleted entry. > > + */ > > +int > > +ext4_remove_dx_entry(handle_t *handle, struct inode *dir, > > + struct dx_frame *dx_frame) > > +{ > > + err = ext4_journal_get_write_access(handle, dx_frame->bh); > > + if (err) { > > + ext4_std_error(dir->i_sb, err); > > + return -EINVAL; > > + } > > + > > + for (; i < count - 1; i++) > > + entries[i] = entries[i + 1]; > > It would be more efficient to do this with "memmove()" rather than copying > each entry separately. Ack, implemented in V2. > > > + /* > > + * If i was 0 when we began above loop, we would have overwritten count > > + * and limit values since those values live in dx_entry->hash of the > > + * first entry. We need to update count but we should set limit as well. > > + */ > > + dx_set_count(entries, count - 1); > > + dx_set_limit(entries, limit); > > How hard is it to avoid clobbering these fields in the first place? > I'm just thinking that "clobber + fixup" is subject to race conditions > at various times in the past, and may become an issue in the future > (e.g. with parallel directory operations). > Ack, I agree better to not clobber in the first place. Implemented in V2. > > static inline bool is_empty_dirent_block(struct inode *dir, > > + struct buffer_head *bh) > > +{ > > This should be combined with ext4_empty_dir() to avoid code duplication. Thanks, this also simplifies ext4_empty_dir(). > > > + struct ext4_dir_entry_2 *de = (struct ext4_dir_entry_2 *)bh->b_data; > > + int csum_size = 0; > > + > > + if (ext4_has_metadata_csum(dir->i_sb) && is_dx(dir)) > > + csum_size = sizeof(struct ext4_dir_entry_tail); > > + > > + return ext4_rec_len_from_disk(de->rec_len, dir->i_sb->s_blocksize) == > > + dir->i_sb->s_blocksize - csum_size && de->inode == 0; > > +} > > This looks like a low cost way to determine the leaf block is empty, > but checking this for every unlink likely has a non-zero cost. Ack > > > @@ -2530,6 +2864,9 @@ static int ext4_delete_entry(handle_t *handle, > > if (unlikely(err)) > > goto out; > > > > + if (is_dx(dir)) > > + ext4_try_dir_shrink(handle, dir, lblk, bh); > > + > > return 0; > > It would be useful to run a comparison benchmark between the patched ext4 > and unpatched when deleting a large number of entries that checks both CPU > usage and performance. That will give us an idea of how much this costs > to be checked for every entry. CPU performance wasn't that different fo both the cases, but there are some differences in overall unlink performance. I added a performance evaluation section in V2. > > Also, rather than calling ext4_try_dir_shrink() and is_empty_dirent_block() > for every entry, couldn't this be returned from ext4_generic_delete_entry(), > since it has that information already. Thanks, implemented this in V2. Thanks, Harshad > > Cheers, Andreas > > > > >
diff --git a/fs/ext4/ext4_jbd2.h b/fs/ext4/ext4_jbd2.h index 7ea4f6fa173b..5b18276c7321 100644 --- a/fs/ext4/ext4_jbd2.h +++ b/fs/ext4/ext4_jbd2.h @@ -83,6 +83,13 @@ */ #define EXT4_INDEX_EXTRA_TRANS_BLOCKS 12U +/* + * Number of credits needed to perform directory shrinking. For each htree + * level, we need 6 blocks (block in question, its parent, last block, last + * block's parent, bitmap block, bg summary). + */ +#define EXT4_DIR_SHRINK_TRANS_BLOCKS 6U + #ifdef CONFIG_QUOTA /* Amount of blocks needed for quota update - we know that the structure was * allocated so we need to update only data block */ diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c index d567b9589875..b78c6f9a6eba 100644 --- a/fs/ext4/namei.c +++ b/fs/ext4/namei.c @@ -275,10 +275,12 @@ static void dx_set_count(struct dx_entry *entries, unsigned value); static void dx_set_limit(struct dx_entry *entries, unsigned value); static unsigned dx_root_limit(struct inode *dir, unsigned infosize); static unsigned dx_node_limit(struct inode *dir); -static struct dx_frame *dx_probe(struct ext4_filename *fname, +static struct dx_frame *__dx_probe(struct ext4_filename *fname, struct inode *dir, struct dx_hash_info *hinfo, - struct dx_frame *frame); + struct dx_frame *frame, + ext4_lblk_t lblk_end, + bool shrink); static void dx_release(struct dx_frame *frames); static int dx_make_map(struct inode *dir, struct ext4_dir_entry_2 *de, unsigned blocksize, struct dx_hash_info *hinfo, @@ -747,15 +749,19 @@ struct stats dx_show_entries(struct dx_hash_info *hinfo, struct inode *dir, /* * Probe for a directory leaf block to search. * - * dx_probe can return ERR_BAD_DX_DIR, which means there was a format + * __dx_probe can return ERR_BAD_DX_DIR, which means there was a format * error in the directory index, and the caller should fall back to - * searching the directory normally. The callers of dx_probe **MUST** + * searching the directory normally. The callers of __dx_probe **MUST** * check for this error code, and make sure it never gets reflected - * back to userspace. + * back to userspace. If lblk_end is set and if __dx_probe hits lblk_end + * logical block, it reads it and stops. If strict is true, __dx_probe + * performs stronger checks for "count" during the lookup. See other + * variants below. */ static struct dx_frame * -dx_probe(struct ext4_filename *fname, struct inode *dir, - struct dx_hash_info *hinfo, struct dx_frame *frame_in) +__dx_probe(struct ext4_filename *fname, struct inode *dir, + struct dx_hash_info *hinfo, struct dx_frame *frame_in, + ext4_lblk_t lblk_end, bool strict) { unsigned count, indirect; struct dx_entry *at, *entries, *p, *q, *m; @@ -820,7 +826,9 @@ dx_probe(struct ext4_filename *fname, struct inode *dir, dxtrace(printk("Look up %x", hash)); while (1) { count = dx_get_count(entries); - if (!count || count > dx_get_limit(entries)) { + /* If we are called from the shrink path */ + if (count > dx_get_limit(entries) || + (strict && !count)) { ext4_warning_inode(dir, "dx entry: count %u beyond limit %u", count, dx_get_limit(entries)); @@ -859,7 +867,7 @@ dx_probe(struct ext4_filename *fname, struct inode *dir, dx_get_block(at))); frame->entries = entries; frame->at = at; - if (!indirect--) + if (!indirect-- || dx_get_block(at) == lblk_end) return frame; frame++; frame->bh = ext4_read_dirblock(dir, dx_get_block(at), INDEX); @@ -889,6 +897,154 @@ dx_probe(struct ext4_filename *fname, struct inode *dir, return ret_err; } +static inline struct dx_frame * +dx_probe(struct ext4_filename *fname, struct inode *dir, + struct dx_hash_info *hinfo, struct dx_frame *frame_in) +{ + return __dx_probe(fname, dir, hinfo, frame_in, 0, true); +} + +/* + * dx_probe with relaxed checks. This function is used in the directory + * shrinking code since we can run into intermediate states where we have + * internal dx nodes with count = 0. + */ +static inline struct dx_frame * +dx_probe_relaxed(struct ext4_filename *fname, struct inode *dir, + struct dx_hash_info *hinfo, struct dx_frame *frame_in) +{ + return __dx_probe(fname, dir, hinfo, frame_in, 0, false); +} + +/* + * Perform only a parttial dx_probe until we find block end_lblk. + */ +static inline struct dx_frame * +dx_probe_partial(struct ext4_filename *fname, struct inode *dir, + struct dx_hash_info *hinfo, struct dx_frame *frame_in, + ext4_lblk_t end_lblk) +{ + return __dx_probe(fname, dir, hinfo, frame_in, end_lblk, false); +} + +/* dx_probe() variant that allows us to lookup frames for a dirent block. */ +struct dx_frame *dx_probe_dirent_blk(struct inode *dir, struct dx_frame *frames, + struct buffer_head *bh, ext4_lblk_t lblk) +{ + struct dx_hash_info hinfo; + struct dx_frame *frame_ptr; + struct ext4_dir_entry_2 *dead_de; + + hinfo.hash_version = EXT4_SB(dir->i_sb)->s_def_hash_version; + if (hinfo.hash_version <= DX_HASH_TEA) + hinfo.hash_version += + EXT4_SB(dir->i_sb)->s_hash_unsigned; + hinfo.seed = EXT4_SB(dir->i_sb)->s_hash_seed; + + /* Let's assume that the lblk is a leaf dirent block */ + dead_de = (struct ext4_dir_entry_2 *)bh->b_data; + ext4fs_dirhash(dir, dead_de->name, dead_de->name_len, &hinfo); + + frame_ptr = dx_probe_relaxed(NULL, dir, &hinfo, frames); + if (!IS_ERR(frame_ptr)) { + /* + * Cross-check if the dead de helped us find the block that we + * are looking to delete. + */ + if (dx_get_block(frame_ptr->at) == lblk) + return frame_ptr; + dx_release(frames); + frame_ptr = ERR_PTR(-EINVAL); + } + return frame_ptr; +} + +/* dx_probe() variant that allows us to lookup frames for a dx node. */ +struct dx_frame *dx_probe_dx_node(struct inode *dir, struct dx_frame *frames, + struct buffer_head *bh, ext4_lblk_t lblk) +{ + struct dx_hash_info hinfo; + struct dx_frame *frame_ptr; + struct dx_entry *entries; + int count; + + hinfo.hash_version = EXT4_SB(dir->i_sb)->s_def_hash_version; + if (hinfo.hash_version <= DX_HASH_TEA) + hinfo.hash_version += + EXT4_SB(dir->i_sb)->s_hash_unsigned; + hinfo.seed = EXT4_SB(dir->i_sb)->s_hash_seed; + entries = ((struct dx_node *)(bh->b_data))->entries; + count = dx_get_count(entries); + if (count > dx_get_limit(entries)) { + ext4_warning_inode(dir, + "dx entry: count %u beyond limit %u", + count, dx_get_limit(entries)); + return ERR_PTR(-EINVAL); + } + + /* Use the first hash found in the dx node */ + hinfo.hash = le32_to_cpu(entries[1].hash); + frame_ptr = dx_probe_partial(NULL, dir, &hinfo, frames, lblk); + if (IS_ERR_OR_NULL(frame_ptr)) + return frame_ptr; + if (dx_get_block(frame_ptr->at) != lblk) { + dx_release(frames); + return ERR_PTR(-EINVAL); + } + + return frame_ptr; +} + +/* + * This function tries to remove the entry of a dirent block (which was just + * emptied by the caller) from the dx frame. It does so by reducing the count by + * 1 and left shifting all the entries after the deleted entry. + */ +int +ext4_remove_dx_entry(handle_t *handle, struct inode *dir, + struct dx_frame *dx_frame) +{ + struct dx_entry *entries; + unsigned int count; + unsigned int limit; + int err, i = 0; + + entries = dx_frame->entries; + count = dx_get_count(entries); + limit = dx_get_limit(entries); + + for (i = 0; i < count; i++) + if (entries[i].block == dx_frame->at->block) + break; + if (i >= count) + return -EINVAL; + + err = ext4_journal_get_write_access(handle, dx_frame->bh); + if (err) { + ext4_std_error(dir->i_sb, err); + return -EINVAL; + } + + for (; i < count - 1; i++) + entries[i] = entries[i + 1]; + + /* + * If i was 0 when we began above loop, we would have overwritten count + * and limit values since those values live in dx_entry->hash of the + * first entry. We need to update count but we should set limit as well. + */ + dx_set_count(entries, count - 1); + dx_set_limit(entries, limit); + + err = ext4_handle_dirty_dx_node(handle, dir, dx_frame->bh); + if (err) { + ext4_std_error(dir->i_sb, err); + return -EINVAL; + } + + return 0; +} + static void dx_release(struct dx_frame *frames) { struct dx_root_info *info; @@ -1413,6 +1569,19 @@ int ext4_search_dir(struct buffer_head *bh, char *search_buf, int buf_size, return 0; } +static inline bool is_empty_dirent_block(struct inode *dir, + struct buffer_head *bh) +{ + struct ext4_dir_entry_2 *de = (struct ext4_dir_entry_2 *)bh->b_data; + int csum_size = 0; + + if (ext4_has_metadata_csum(dir->i_sb) && is_dx(dir)) + csum_size = sizeof(struct ext4_dir_entry_tail); + + return ext4_rec_len_from_disk(de->rec_len, dir->i_sb->s_blocksize) == + dir->i_sb->s_blocksize - csum_size && de->inode == 0; +} + static int is_dx_internal_node(struct inode *dir, ext4_lblk_t block, struct ext4_dir_entry *de) { @@ -2496,6 +2665,171 @@ int ext4_generic_delete_entry(handle_t *handle, return -ENOENT; } +static void make_unindexed(handle_t *handle, struct inode *dir, + struct buffer_head *bh) +{ + struct ext4_dir_entry_2 *de; + int parent_ino, csum_size = 0; + + de = (struct ext4_dir_entry_2 *)bh->b_data; + parent_ino = le32_to_cpu( + ((struct dx_root *)bh->b_data)->dotdot.inode); + if (ext4_has_metadata_csum(dir->i_sb)) + csum_size = sizeof(struct ext4_dir_entry_tail); + memset(bh->b_data, 0, dir->i_sb->s_blocksize); + ext4_init_dot_dotdot(dir, de, dir->i_sb->s_blocksize, csum_size, + parent_ino, 0); + if (csum_size) + ext4_initialize_dirent_tail(bh, dir->i_sb->s_blocksize); + ext4_handle_dirty_dirblock(handle, dir, bh); + ext4_clear_inode_flag(dir, EXT4_INODE_INDEX); + ext4_mark_inode_dirty(handle, dir); +} + +/* + * Copy contents from lblk_src to lblk_dst and remap internal dx nodes + * such that parent of lblk_src points to lblk_dst. + */ +static int ext4_dx_remap_block(handle_t *handle, struct inode *dir, + struct buffer_head *bh_dst, + ext4_lblk_t lblk_dst, ext4_lblk_t lblk_src) +{ + struct dx_frame frames[EXT4_HTREE_LEVEL], *frame_ptr; + struct buffer_head *bh_src; + int ret; + + bh_src = ext4_bread(handle, dir, lblk_src, 0); + if (IS_ERR_OR_NULL(bh_src)) + return -EIO; + + memset(frames, 0, sizeof(frames)); + + /* + * blk_src can either be a dirent block or dx node. Try to search + * using both and use whichever one that returns success. + */ + frame_ptr = dx_probe_dirent_blk(dir, frames, bh_src, lblk_src); + if (IS_ERR_OR_NULL(frame_ptr)) { + frame_ptr = dx_probe_dx_node(dir, frames, bh_src, lblk_src); + if (IS_ERR_OR_NULL(frame_ptr)) { + brelse(bh_src); + return PTR_ERR(frame_ptr); + } + } + + memcpy(bh_dst->b_data, bh_src->b_data, bh_dst->b_size); + frame_ptr->at->block = cpu_to_le32(lblk_dst); + + /* Set pointer in bh_last_parent to bh */ + ret = ext4_journal_get_write_access(handle, bh_src); + if (ret) + goto out; + + ret = ext4_journal_get_write_access(handle, frame_ptr->bh); + if (ret) + goto out; + + ret = ext4_handle_dirty_metadata(handle, dir, bh_src); + if (ret) { + ext4_std_error(dir->i_sb, ret); + goto out; + } + + ret = ext4_handle_dirty_dx_node(handle, dir, frame_ptr->bh); + if (ret) { + ext4_std_error(dir->i_sb, ret); + goto out; + } +out: + brelse(bh_src); + dx_release(frames); + return ret; +} + +/* + * Try to shrink directory as much as possible. This function + * truncates directory to the new size. + * + * The high level algorithm is as follows: + * + * - If after dentry removal the dirent block (let's call it B) becomes + * empty, then remove its references in its dx parent. + * - Swap its contents with that of the last block (L) in directory. + * - Update L's parents to point to B instead. + * - Remove L + * - Repeat this for all the ancestors of B. + */ +static int ext4_try_dir_shrink(handle_t *handle, struct inode *dir, + ext4_lblk_t lblk, struct buffer_head *bh) +{ + struct buffer_head *bh_last = NULL, *parent_bh = NULL; + struct dx_frame frames[EXT4_HTREE_LEVEL], *frame_ptr; + ext4_lblk_t shrink = 0, last_lblk, parent_lblk; + int ret = 0; + bool check_empty; + + memset(frames, 0, sizeof(frames)); + frame_ptr = dx_probe_dirent_blk(dir, frames, bh, lblk); + if (IS_ERR(frame_ptr)) + return -EINVAL; + + last_lblk = (dir->i_size >> dir->i_sb->s_blocksize_bits) - 1; + + check_empty = is_empty_dirent_block(dir, bh); + while (check_empty && frame_ptr >= frames) { + parent_lblk = frame_ptr > frames ? + dx_get_block((frame_ptr - 1)->at) : 0; + lblk = dx_get_block(frame_ptr->at); + if (ext4_journal_extend( + handle, EXT4_DIR_SHRINK_TRANS_BLOCKS, 0) < 0) + break; + if (ext4_remove_dx_entry(handle, dir, frame_ptr) < 0) + break; + check_empty = dx_get_count(frame_ptr->entries) == 0; + if (lblk != last_lblk) { + ret = ext4_dx_remap_block(handle, dir, bh, lblk, + last_lblk); + if (ret) + break; + } + + if (parent_lblk == last_lblk) + parent_lblk = lblk; + last_lblk--; + shrink++; + + if (parent_lblk == 0) + break; + if (!IS_ERR_OR_NULL(parent_bh)) + brelse(parent_bh); + parent_bh = ext4_bread(handle, dir, parent_lblk, 0); + if (IS_ERR_OR_NULL(parent_bh)) + break; + dx_release(frames); + frame_ptr = dx_probe_dx_node(dir, frames, parent_bh, + parent_lblk); + if (IS_ERR(frame_ptr)) + break; + bh = parent_bh; + } + + /* Fallback to linear directories if root node becomes empty */ + if (dx_get_count(frames[0].entries) == 0) + make_unindexed(handle, dir, frames[0].bh); + if (!IS_ERR(frame_ptr)) + dx_release(frames); + if (!IS_ERR_OR_NULL(bh_last)) + brelse(bh_last); + if (!IS_ERR_OR_NULL(parent_bh)) + brelse(parent_bh); + + if (ret || !shrink) + return ret; + + dir->i_size -= shrink * dir->i_sb->s_blocksize; + return ext4_truncate(dir); +} + static int ext4_delete_entry(handle_t *handle, struct inode *dir, struct ext4_dir_entry_2 *de_del, @@ -2530,6 +2864,9 @@ static int ext4_delete_entry(handle_t *handle, if (unlikely(err)) goto out; + if (is_dx(dir)) + ext4_try_dir_shrink(handle, dir, lblk, bh); + return 0; out: if (err != -ENOENT)
This patch adds shrinking support for htree based directories. The high level algorithm is as follows: * If after dentry removal the dirent block (let's call it B) becomes empty, then remove its references in its dx parent. * Swap its contents with that of the last block (L) in directory. * Update L's parents to point to B instead. * Remove L * Repeat this for all the ancestors of B. We add variants of dx_probe that allow us perform reverse lookups from a logical block to its dx parents. Ran kvm-xfstests smoke and verified that no new failures are introduced. Ran shrinking for directories with following number of files and then deleted files one by one: * 1000 (size before deletion 36K, after deletion 4K) * 10000 (size before deletion 196K, after deletion 4K) * 100000 (size before deletion 2.1M, after deletion 4K) * 200000 (size before deletion 4.2M, after deletion 4K) In all cases directory shrunk significantly. We fallback to linear directories if the directory becomes empty. But note that most of the shrinking happens during last 1-2% deletions in an average case. Therefore, the next step here is to merge dx nodes when possible. That can be achieved by storing the fullness index in htree nodes. But that's an on-disk format change. We can instead build on tooling added by this patch to perform reverse lookup on a dx node and then reading adjacent nodes to check their fullness. This patch supersedes the other directory shrinking patch sent in Aug 2019 ("ext4: attempt to shrink directory on dentry removal"). Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com> --- fs/ext4/ext4_jbd2.h | 7 + fs/ext4/namei.c | 355 ++++++++++++++++++++++++++++++++++++++++++-- 2 files changed, 353 insertions(+), 9 deletions(-)