From: Matthew Wilcox <willy@infradead.org>
To: Brian Geffon <bgeffon@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-block@vger.kernel.org, linnux-mm@kvack.org
Subject: Re: [PATCH] zram: Add a huge_idle writeback mode
Date: Tue, 15 Mar 2022 17:28:03 +0000 [thread overview]
Message-ID: <YjDMo35Q/cvPLkxu@casper.infradead.org> (raw)
In-Reply-To: <20220315172221.9522-1-bgeffon@google.com>
On Tue, Mar 15, 2022 at 10:22:21AM -0700, Brian Geffon wrote:
> Today it's only possible to write back as a page, idle, or huge.
> A user might want to writeback pages which are huge and idle first
> as these idle pages do not require decompression and make a good
> first pass for writeback.
We're moving towards having many different sizes of page in play,
not just PMD and PTE sizes. Is this patch actually a good idea in
a case where we have, eg, a 32kB anonymous page on a system with 4kB
pages? How should zram handle this case? What's our cut-off for
declaring a page to be "huge"?
next prev parent reply other threads:[~2022-03-15 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 17:22 [PATCH] zram: Add a huge_idle writeback mode Brian Geffon
2022-03-15 17:28 ` Matthew Wilcox [this message]
2022-03-15 17:34 ` Brian Geffon
2022-03-15 17:44 ` Matthew Wilcox
2022-03-16 0:01 ` Brian Geffon
2022-03-18 16:41 ` Minchan Kim
2022-03-18 16:51 ` Brian Geffon
2022-03-18 17:30 ` Minchan Kim
2022-03-21 14:50 ` Brian Geffon
2022-03-22 21:13 ` Minchan Kim
2022-03-22 21:52 ` Brian Geffon
2022-03-22 21:58 ` [PATCH v2] " Brian Geffon
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=YjDMo35Q/cvPLkxu@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=linnux-mm@kvack.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.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;
as well as URLs for NNTP newsgroup(s).