From: Zhang Yi <yi.zhang@huawei.com>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tytso@mit.edu>, <jack@suse.com>
Subject: Re: [PATCH v3 4/8] jbd2: remove unneeded kmap for jh_in->b_frozen_data in jbd2_journal_write_metadata_buffer
Date: Wed, 31 Jul 2024 19:54:56 +0800 [thread overview]
Message-ID: <e3fc4766-ce2b-b7d3-abcf-f145c2ff2727@huawei.com> (raw)
In-Reply-To: <20240731092910.2383048-5-shikemeng@huaweicloud.com>
On 2024/7/31 17:29, Kemeng Shi wrote:
> Remove kmap for page of b_frozen_data from jbd2_alloc() which always
> provides an address from the direct kernel mapping.
>
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
> Reviewed-by: Jan Kara <jack@suse.cz>
Looks good to me.
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
> ---
> fs/jbd2/journal.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
> index 312c7575b54f..9c1ffb0dc740 100644
> --- a/fs/jbd2/journal.c
> +++ b/fs/jbd2/journal.c
> @@ -352,12 +352,13 @@ int jbd2_journal_write_metadata_buffer(transaction_t *transaction,
> done_copy_out = 1;
> new_folio = virt_to_folio(jh_in->b_frozen_data);
> new_offset = offset_in_folio(new_folio, jh_in->b_frozen_data);
> + mapped_data = jh_in->b_frozen_data;
> } else {
> new_folio = bh_in->b_folio;
> new_offset = offset_in_folio(new_folio, bh_in->b_data);
> + mapped_data = kmap_local_folio(new_folio, new_offset);
> }
>
> - mapped_data = kmap_local_folio(new_folio, new_offset);
> /*
> * Fire data frozen trigger if data already wasn't frozen. Do this
> * before checking for escaping, as the trigger may modify the magic
> @@ -373,7 +374,8 @@ int jbd2_journal_write_metadata_buffer(transaction_t *transaction,
> */
> if (*((__be32 *)mapped_data) == cpu_to_be32(JBD2_MAGIC_NUMBER))
> do_escape = 1;
> - kunmap_local(mapped_data);
> + if (!jh_in->b_frozen_data)
> + kunmap_local(mapped_data);
>
> /*
> * Do we need to do a data copy?
>
next prev parent reply other threads:[~2024-07-31 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 9:29 [PATCH v3 0/8] Fix and cleanups to jbd2 Kemeng Shi
2024-07-31 9:29 ` [PATCH v3 1/8] jbd2: correctly compare tids with tid_geq function in jbd2_fc_begin_commit Kemeng Shi
2024-07-31 9:29 ` [PATCH v3 2/8] jbd2: remove dead check in journal_alloc_journal_head Kemeng Shi
2024-07-31 9:29 ` [PATCH v3 3/8] jbd2: remove unused return value of jbd2_fc_release_bufs Kemeng Shi
2024-07-31 9:29 ` [PATCH v3 4/8] jbd2: remove unneeded kmap for jh_in->b_frozen_data in jbd2_journal_write_metadata_buffer Kemeng Shi
2024-07-31 11:54 ` Zhang Yi [this message]
2024-07-31 9:29 ` [PATCH v3 5/8] jbd2: remove unneeded done_copy_out variable " Kemeng Shi
2024-07-31 11:57 ` Zhang Yi
2024-07-31 9:29 ` [PATCH v3 6/8] ext4: move escape handle to futher improve jbd2_journal_write_metadata_buffer Kemeng Shi
2024-07-31 12:07 ` Zhang Yi
2024-07-31 12:17 ` Zhang Yi
2024-08-01 1:24 ` Kemeng Shi
2024-08-07 7:41 ` wangjianjian (C)
2024-08-08 5:30 ` Kemeng Shi
2024-07-31 9:29 ` [PATCH v3 7/8] jbd2: correct comment jbd2_mark_journal_empty Kemeng Shi
2024-07-31 9:29 ` [PATCH v3 8/8] jbd2: remove unneeded check of ret in jbd2_fc_get_buf Kemeng Shi
2024-07-31 12:08 ` Zhang Yi
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=e3fc4766-ce2b-b7d3-abcf-f145c2ff2727@huawei.com \
--to=yi.zhang@huawei.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shikemeng@huaweicloud.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
all inboxes | Powered by JetHome®