From: Andreas Dilger <adilger@dilger.ca>
To: brookxu <brookxu.cn@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] ext4: reorganize if statement of ext4_mb_release_context()
Date: Tue, 4 Aug 2020 22:43:24 -0600 [thread overview]
Message-ID: <7FA38CCB-BDB3-4D35-AA73-C7604B0BCC87@dilger.ca> (raw)
In-Reply-To: <ad1ac152-6d52-13cd-5786-7c888bf9370d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
On Aug 4, 2020, at 7:01 PM, brookxu <brookxu.cn@gmail.com> wrote:
>
> Reorganize the if statement of ext4_mb_release_context(), make it
> easier to read.
>
> Signed-off-by: Chunguang Xu <brookxu@tencent.com>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
> ---
> fs/ext4/mballoc.c | 27 +++++++++++++--------------
> 1 file changed, 13 insertions(+), 14 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index c0a331e..4f21f34 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -4564,20 +4564,19 @@ static int ext4_mb_release_context(struct ext4_allocation_context *ac)
> pa->pa_free -= ac->ac_b_ex.fe_len;
> pa->pa_len -= ac->ac_b_ex.fe_len;
> spin_unlock(&pa->pa_lock);
> - }
> - }
> - if (pa) {
> - /*
> - * We want to add the pa to the right bucket.
> - * Remove it from the list and while adding
> - * make sure the list to which we are adding
> - * doesn't grow big.
> - */
> - if ((pa->pa_type == MB_GROUP_PA) && likely(pa->pa_free)) {
> - spin_lock(pa->pa_obj_lock);
> - list_del_rcu(&pa->pa_inode_list);
> - spin_unlock(pa->pa_obj_lock);
> - ext4_mb_add_n_trim(ac);
> +
> + /*
> + * We want to add the pa to the right bucket.
> + * Remove it from the list and while adding
> + * make sure the list to which we are adding
> + * doesn't grow big.
> + */
> + if (likely(pa->pa_free)) {
> + spin_lock(pa->pa_obj_lock);
> + list_del_rcu(&pa->pa_inode_list);
> + spin_unlock(pa->pa_obj_lock);
> + ext4_mb_add_n_trim(ac);
> + }
> }
> ext4_mb_put_pa(ac, ac->ac_sb, pa);
> }
>
> --
> 1.8.3.1
>
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
prev parent reply other threads:[~2020-08-05 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 1:01 brookxu
2020-08-05 4:43 ` Andreas Dilger [this message]
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=7FA38CCB-BDB3-4D35-AA73-C7604B0BCC87@dilger.ca \
--to=adilger@dilger.ca \
--cc=brookxu.cn@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®