From: Brian Geffon <bgeffon@google.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>,
Nitin Gupta <ngupta@vflare.org>,
LKML <linux-kernel@vger.kernel.org>,
Suleiman Souhlal <suleiman@google.com>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC PATCH 1/1] zram: Allow rw_page when page isn't written back.
Date: Wed, 10 Aug 2022 15:18:54 -0400 [thread overview]
Message-ID: <CADyq12wAUyo4=Wya4zvD6RiVdqcwwcMqZ3xEDa1k6jVY0_o_jg@mail.gmail.com> (raw)
In-Reply-To: <YvG6fDHmVITsa/Kk@google.com>
Thanks Sergey,
On Mon, Aug 8, 2022 at 9:38 PM Sergey Senozhatsky
<senozhatsky@chromium.org> wrote:
>
> On (22/08/08 12:50), Brian Geffon wrote:
> [..]
> >
> > pr_info("setup backing device %s\n", file_name);
> > @@ -722,7 +707,8 @@ static ssize_t writeback_store(struct device *dev,
> >
> > if (zram_test_flag(zram, index, ZRAM_WB) ||
> > zram_test_flag(zram, index, ZRAM_SAME) ||
> > - zram_test_flag(zram, index, ZRAM_UNDER_WB))
> > + zram_test_flag(zram, index, ZRAM_UNDER_WB) ||
> > + zram_test_flag(zram, index, ZRAM_NO_WB))
> > goto next;
>
> mark_idle() probably should also test ZRAM_NO_WB bit.
While we definitely can add that check in mark_idle() it actually
doesn't hurt to allow marking the page as idle as NO_WB only controls
the writeback aspect and as long as the page is marked NO_WB it won't
be written back, idle or not. Definitely happy to add it in later
versions if people like this approach in general.
prev parent reply other threads:[~2022-08-10 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 16:50 [RFC PATCH 0/1] " Brian Geffon
2022-08-08 16:50 ` [RFC PATCH 1/1] " Brian Geffon
2022-08-09 1:38 ` Sergey Senozhatsky
2022-08-10 19:18 ` Brian Geffon [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='CADyq12wAUyo4=Wya4zvD6RiVdqcwwcMqZ3xEDa1k6jVY0_o_jg@mail.gmail.com' \
--to=bgeffon@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.org \
--cc=suleiman@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