From: Jan Kara <jack@suse.cz>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: Jan Kara <jack@suse.cz>, Ted Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>,
Stefan Wahren <stefan.wahren@i2se.com>,
Andreas Dilger <adilger.kernel@dilger.ca>
Subject: Re: [PATCH 5/5] ext4: Use buckets for cr 1 block scan instead of rbtree
Date: Thu, 8 Sep 2022 11:03:23 +0200 [thread overview]
Message-ID: <20220908090323.e4enzh5ahxxw64ic@quack3> (raw)
In-Reply-To: <YxmoBpQdRqh/e4ol@li-bb2b2a4c-3307-11b2-a85c-8fa5c3a69313.ibm.com>
On Thu 08-09-22 13:59:58, Ojaswin Mujoo wrote:
> Hi Jan,
>
> On Tue, Sep 06, 2022 at 05:29:11PM +0200, Jan Kara wrote:
> >
> > ** snip **
> > /*
> > * Choose next group by traversing average fragment size tree. Updates *new_cr
> Maybe we can change this to "average fragment size list of suitable
> order"
Right. Fixed. Thanks for catching this.
> > - * if cr lvel needs an update. Sets EXT4_MB_SEARCH_NEXT_LINEAR to indicate that
> > - * the linear search should continue for one iteration since there's lock
> > - * contention on the rb tree lock.
> > + * if cr level needs an update.
> > */
> > static void ext4_mb_choose_next_group_cr1(struct ext4_allocation_context *ac,
> > int *new_cr, ext4_group_t *group, ext4_group_t ngroups)
> > {
> > struct ext4_sb_info *sbi = EXT4_SB(ac->ac_sb);
> > - int avg_fragment_size, best_so_far;
> > - struct rb_node *node, *found;
> > - struct ext4_group_info *grp;
>
> Other than that, this patch along with the updated mb_structs_summary
> proc file change looks good to me.
Thanks for review & testing!
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-09-08 9:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 15:29 [PATCH 0/5 v2] ext4: Fix performance regression with mballoc Jan Kara
2022-09-06 15:29 ` [PATCH 1/5] ext4: Make mballoc try target group first even with mb_optimize_scan Jan Kara
2022-09-07 17:43 ` Ritesh Harjani (IBM)
2022-09-06 15:29 ` [PATCH 2/5] ext4: Avoid unnecessary spreading of allocations among groups Jan Kara
2022-09-07 18:05 ` Ritesh Harjani (IBM)
2022-09-08 8:57 ` Jan Kara
2022-09-08 9:24 ` Ritesh Harjani (IBM)
2022-09-06 15:29 ` [PATCH 3/5] ext4: Make directory inode spreading reflect flexbg size Jan Kara
2022-09-06 15:29 ` [PATCH 4/5] ext4: Use locality group preallocation for small closed files Jan Kara
2022-09-07 18:25 ` Ritesh Harjani (IBM)
2022-09-06 15:29 ` [PATCH 5/5] ext4: Use buckets for cr 1 block scan instead of rbtree Jan Kara
2022-09-07 18:41 ` Ritesh Harjani (IBM)
2022-09-08 9:01 ` Jan Kara
2022-09-08 9:23 ` Ritesh Harjani (IBM)
2022-09-08 8:29 ` Ojaswin Mujoo
2022-09-08 9:03 ` Jan Kara [this message]
2022-09-08 11:00 ` Dan Carpenter
2022-09-08 11:33 ` Jan Kara
2022-09-06 20:38 ` [PATCH 0/5 v2] ext4: Fix performance regression with mballoc Stefan Wahren
2022-09-07 10:49 ` Jan Kara
2022-09-07 13:02 ` Jan Kara
2022-09-08 8:17 ` Ojaswin Mujoo
2022-09-08 9:12 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2022-09-08 9:21 [PATCH 0/5 v3] " Jan Kara
2022-09-08 9:21 ` [PATCH 5/5] ext4: Use buckets for cr 1 block scan instead of rbtree Jan Kara
2022-09-09 6:12 ` Ritesh Harjani (IBM)
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=20220908090323.e4enzh5ahxxw64ic@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=regressions@leemhuis.info \
--cc=stefan.wahren@i2se.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