From: Usama Arif <usamaarif642@gmail.com>
To: Chengming Zhou <chengming.zhou@linux.dev>, akpm@linux-foundation.org
Cc: willy@infradead.org, hannes@cmpxchg.org, yosryahmed@google.com,
nphamcs@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
Shakeel Butt <shakeel.butt@linux.dev>
Subject: Re: [PATCH] mm: Do not start/end writeback for pages stored in zswap
Date: Tue, 11 Jun 2024 16:59:11 +0100 [thread overview]
Message-ID: <227d931f-18b8-48d5-8306-64940fcf1425@gmail.com> (raw)
In-Reply-To: <5d051998-015c-4da4-83f0-1b4fb9009c68@linux.dev>
On 11/06/2024 10:53, Chengming Zhou wrote:
> On 2024/6/10 22:30, Usama Arif wrote:
>> start/end writeback combination incorrectly increments NR_WRITTEN
>> counter, eventhough the pages aren't written to disk. Pages successfully
>> stored in zswap should just unlock folio and return from writepage.
>>
>> Signed-off-by: Usama Arif <usamaarif642@gmail.com>
> Looks good to me, thanks.
>
> Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
Fororgot to add:
Suggested-by: Matthew Wilcox (Oracle) <willy@infradead.org>
>
>> ---
>> mm/page_io.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/mm/page_io.c b/mm/page_io.c
>> index a360857cf75d..501784d79977 100644
>> --- a/mm/page_io.c
>> +++ b/mm/page_io.c
>> @@ -196,9 +196,7 @@ int swap_writepage(struct page *page, struct writeback_control *wbc)
>> return ret;
>> }
>> if (zswap_store(folio)) {
>> - folio_start_writeback(folio);
>> folio_unlock(folio);
>> - folio_end_writeback(folio);
>> return 0;
>> }
>> if (!mem_cgroup_zswap_writeback_enabled(folio_memcg(folio))) {
next prev parent reply other threads:[~2024-06-11 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 14:30 Usama Arif
2024-06-10 17:31 ` Yosry Ahmed
2024-06-10 18:11 ` Usama Arif
2024-06-10 18:29 ` Yosry Ahmed
2024-06-10 19:08 ` Shakeel Butt
2024-06-10 20:05 ` Yosry Ahmed
2024-06-10 20:15 ` Johannes Weiner
2024-06-11 9:53 ` Chengming Zhou
2024-06-11 15:59 ` Usama Arif [this message]
2024-06-11 17:16 ` Shakeel Butt
2024-06-11 17:28 ` Yosry Ahmed
2024-06-12 10:01 Usama Arif
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=227d931f-18b8-48d5-8306-64940fcf1425@gmail.com \
--to=usamaarif642@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=willy@infradead.org \
--cc=yosryahmed@google.com \
/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