linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengnan Chang <changfengnan@bytedance.com>
To: Guoqing Jiang <guoqing.jiang@linux.dev>
Cc: adilger.kernel@dilger.ca, tytso@mit.edu,
	linux-ext4@vger.kernel.org,
	kernel test robot <oliver.sang@intel.com>
Subject: Re: [External] Re: [PATCH v3] ext4: improve trim efficiency
Date: Mon, 31 Jul 2023 20:52:06 +0800	[thread overview]
Message-ID: <CAPFOzZurP23oCENeP57f7Kj-4uCf9bN9ERZQTbdZJh_d5rUEwg@mail.gmail.com> (raw)
In-Reply-To: <810f6c3a-89a1-837f-fd79-46f1fd32bbe7@linux.dev>

Hi Ted, Andreas:
    Any comments ?

Thanks.

Guoqing Jiang <guoqing.jiang@linux.dev> 于2023年7月31日周一 10:27写道:
>
>
>
> On 7/25/23 20:18, Fengnan Chang wrote:
> > In commit a015434480dc("ext4: send parallel discards on commit
> > completions"), issue all discard commands in parallel make all
> > bios could merged into one request, so lowlevel drive can issue
> > multi segments in one time which is more efficiency, but commit
> > 55cdd0af2bc5 ("ext4: get discard out of jbd2 commit kthread contex")
> > seems broke this way, let's fix it.
> > In my test:
> > 1. create 10 normal files, each file size is 10G.
> > 2. deallocate file, punch a 16k holes every 32k.
> > 3. trim all fs.
> >
> > the time of fstrim fs reduce from 6.7s to 1.3s.
> >
> > Reported-by: kernel test robot <oliver.sang@intel.com>
> > Closes: https://lore.kernel.org/oe-lkp/202307171455.ee68ef8b-oliver.sang@intel.com
> > Signed-off-by: Fengnan Chang <changfengnan@bytedance.com>
> > ---
> >   fs/ext4/mballoc.c | 49 +++++++++++++++++++++++++++++++++++++++++------
> >   1 file changed, 43 insertions(+), 6 deletions(-)
> >
> > diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> > index a2475b8c9fb5..b75ca1df0d30 100644
> > --- a/fs/ext4/mballoc.c
> > +++ b/fs/ext4/mballoc.c
> > @@ -6790,7 +6790,8 @@ int ext4_group_add_blocks(handle_t *handle, struct super_block *sb,
> >    * be called with under the group lock.
> >    */
> >   static int ext4_trim_extent(struct super_block *sb,
> > -             int start, int count, struct ext4_buddy *e4b)
> > +             int start, int count, bool noalloc, struct ext4_buddy *e4b,
> > +             struct bio **biop, struct ext4_free_data **entryp)
> >   __releases(bitlock)
> >   __acquires(bitlock)
> >   {
> > @@ -6812,9 +6813,16 @@ __acquires(bitlock)
> >        */
> >       mb_mark_used(e4b, &ex);
> >       ext4_unlock_group(sb, group);
> > -     ret = ext4_issue_discard(sb, group, start, count, NULL);
> > +     ret = ext4_issue_discard(sb, group, start, count, biop);
> > +     if (!ret && !noalloc) {
> > +             struct ext4_free_data *entry = kmem_cache_alloc(ext4_free_data_cachep,
> > +                             GFP_NOFS|__GFP_NOFAIL);
> > +             entry->efd_start_cluster = start;
> > +             entry->efd_count = count;
> > +             *entryp  = entry;
> > +     }
> > +
> >       ext4_lock_group(sb, group);
> > -     mb_free_blocks(NULL, e4b, start, ex.fe_len);
> >       return ret;
> >   }
> >
> > @@ -6824,26 +6832,40 @@ static int ext4_try_to_trim_range(struct super_block *sb,
> >   __acquires(ext4_group_lock_ptr(sb, e4b->bd_group))
> >   __releases(ext4_group_lock_ptr(sb, e4b->bd_group))
> >   {
> > -     ext4_grpblk_t next, count, free_count;
> > +     ext4_grpblk_t next, count, free_count, bak;
> >       void *bitmap;
> > +     struct ext4_free_data *entry = NULL, *fd, *nfd;
> > +     struct list_head discard_data_list;
> > +     struct bio *discard_bio = NULL;
> > +     struct blk_plug plug;
> > +     bool noalloc = false;
> > +
> > +     INIT_LIST_HEAD(&discard_data_list);
> >
> >       bitmap = e4b->bd_bitmap;
> >       start = (e4b->bd_info->bb_first_free > start) ?
> >               e4b->bd_info->bb_first_free : start;
> >       count = 0;
> >       free_count = 0;
> > +     bak = start;
> >
> > +     blk_start_plug(&plug);
> >       while (start <= max) {
> >               start = mb_find_next_zero_bit(bitmap, max + 1, start);
> >               if (start > max)
> >                       break;
> >               next = mb_find_next_bit(bitmap, max + 1, start);
> > +             /* when only one segment, there is no need to alloc entry */
> > +             noalloc = (free_count == 0) && (next >= max);
> >
> >               if ((next - start) >= minblocks) {
> > -                     int ret = ext4_trim_extent(sb, start, next - start, e4b);
> > +                     int ret = ext4_trim_extent(sb, start, next - start, noalloc, e4b,
> > +                                                     &discard_bio, &entry);
> >
> > -                     if (ret && ret != -EOPNOTSUPP)
> > +                     if (ret < 0)
> >                               break;
> > +                     if (entry)
> > +                             list_add_tail(&entry->efd_list, &discard_data_list);
> >                       count += next - start;
> >               }
> >               free_count += next - start;
> > @@ -6863,6 +6885,21 @@ __releases(ext4_group_lock_ptr(sb, e4b->bd_group))
> >               if ((e4b->bd_info->bb_free - free_count) < minblocks)
> >                       break;
> >       }
> > +     if (discard_bio) {
> > +             ext4_unlock_group(sb, e4b->bd_group);
> > +             submit_bio_wait(discard_bio);
> > +             bio_put(discard_bio);
> > +             ext4_lock_group(sb, e4b->bd_group);
> > +     }
> > +     blk_finish_plug(&plug);
> > +
> > +     if (noalloc)
> > +             mb_free_blocks(NULL, e4b, bak, free_count);
> > +
> > +     list_for_each_entry_safe(fd, nfd, &discard_data_list, efd_list) {
> > +             mb_free_blocks(NULL, e4b, fd->efd_start_cluster, fd->efd_count);
> > +             kmem_cache_free(ext4_free_data_cachep, fd);
> > +     }
> >
> >       return count;
> >   }
>
> With the new version, I don't see big difference from my test.
>
> Thanks,
> Guoqing

  reply	other threads:[~2023-07-31 12:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 12:18 [PATCH v3] ext4: improve trim efficiency Fengnan Chang
2023-07-31  2:26 ` Guoqing Jiang
2023-07-31 12:52   ` Fengnan Chang [this message]
2023-08-09  8:20     ` [External] " Fengnan Chang
2023-08-18  3:43 ` Theodore Ts'o
2023-08-18  7:14   ` [External] " Fengnan Chang
2023-08-18 16:55     ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPFOzZurP23oCENeP57f7Kj-4uCf9bN9ERZQTbdZJh_d5rUEwg@mail.gmail.com \
    --to=changfengnan@bytedance.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=guoqing.jiang@linux.dev \
    --cc=linux-ext4@vger.kernel.org \
    --cc=oliver.sang@intel.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).