From: Qu Wenruo <wqu@suse.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: enhance function extent_range_clear_dirty_for_io()
Date: Mon, 20 May 2024 20:36:57 +0930 [thread overview]
Message-ID: <48ed0d56-7a14-4216-9f85-cd2a48e592aa@suse.com> (raw)
In-Reply-To: <CAL3q7H7RxYhiTTMZU_qQ9yZKRm7Qo_YdhDq1zNxz=g_gVALhcw@mail.gmail.com>
在 2024/5/20 20:21, Filipe Manana 写道:
> On Mon, May 20, 2024 at 4:56 AM Qu Wenruo <wqu@suse.com> wrote:
[...]
>> - Make it subpage compatible
>> Although currently compression only happens in a full page basis even
>> for subpage routine, there is no harm to make it subpage compatible
>> now.
>
> The changes seem ok and reasonable to me.
>
> However I think these are really 3 separate changes that should be in
> 3 different patches.
> It makes it easier to review and to revert in case there's a need to do so.
>
> So I would make the move to inode.c first, and then the other changes.
> Or the move last in case we need to backport the other changes.
Sure, that indeed sounds better
[...]
>> + if (missing_folio)
>> + return -ENOENT;
>
> Why not return the error from filemap_get_folio()? We could keep it
> and then return it after finishing the loop.
> Currently it can only return -ENOENT, according to the function's
> comment, but it would be better future proof and return whatever error
> it returns.
Sure, although we can only either keep the first or the last error.
Thanks,
Qu
>
> Thanks.
>
>> + return 0;
>> +}
>> +
>> /*
>> * Work queue call back to started compression on a file and pages.
>> *
>> @@ -931,7 +957,10 @@ static void compress_file_range(struct btrfs_work *work)
>> * Otherwise applications with the file mmap'd can wander in and change
>> * the page contents while we are compressing them.
>> */
>> - extent_range_clear_dirty_for_io(&inode->vfs_inode, start, end);
>> + ret = extent_range_clear_dirty_for_io(&inode->vfs_inode, start, end);
>> +
>> + /* We have locked all the involved pagse, shouldn't hit a missing page. */
>> + ASSERT(ret == 0);
>>
>> /*
>> * We need to save i_size before now because it could change in between
>> --
>> 2.45.1
>>
>>
prev parent reply other threads:[~2024-05-20 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 3:55 [PATCH] btrfs: enhance function extent_range_clear_dirty_for_io() Qu Wenruo
2024-05-20 10:51 ` Filipe Manana
2024-05-20 11:06 ` Qu Wenruo [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=48ed0d56-7a14-4216-9f85-cd2a48e592aa@suse.com \
--to=wqu@suse.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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