[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b8e24ac-500e-4d53-acbe-a9f97794a498@kernel.org>
Date: Wed, 7 May 2025 15:09:35 +0800
From: Chao Yu <chao@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: chao@...nel.org, Jaegeuk Kim <jaegeuk@...nel.org>,
linux-f2fs-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] f2fs: don't return AOP_WRITEPAGE_ACTIVATE from
f2fs_write_single_data_page
On 5/7/25 14:44, Christoph Hellwig wrote:
> On Wed, May 07, 2025 at 02:28:55PM +0800, Chao Yu wrote:
>>> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
>>> index e016b0f96313..ce63b3bfb28f 100644
>>> --- a/fs/f2fs/compress.c
>>> +++ b/fs/f2fs/compress.c
>>> @@ -1565,10 +1565,7 @@ static int f2fs_write_raw_pages(struct compress_ctx *cc,
>>> NULL, NULL, wbc, io_type,
>>> compr_blocks, false);
>>> if (ret) {
>>> - if (ret == AOP_WRITEPAGE_ACTIVATE) {
>>> - folio_unlock(folio);
>>> - ret = 0;
>>
>> Previously, for this case, it will goto out label rather than writing
>> left pages?
>
> Indeed. Is that the right thing to do here?
IIRC, once it failed to write one page, it redirties all left pages, and tries
to rewrite them again, it can avoid fragment as much as possible.
So can we keep original implementation here?
Thanks,
Powered by blists - more mailing lists