From: Dan Streetman <ddstreet@ieee.org>
To: Li Wang <liwang@redhat.com>
Cc: Linux-MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Seth Jennings <sjenning@redhat.com>,
Huang Ying <huang.ying.caritas@gmail.com>,
Yu Zhao <yuzhao@google.com>
Subject: Re: [PATCH RFC] zswap: reject to compress/store page if zswap_max_pool_percent is 0
Date: Tue, 29 May 2018 17:14:39 -0400 [thread overview]
Message-ID: <CALZtONA4y+7vzUr2xPa8ZbwCczjJV9EMCOXaCsE94DdfGbrmtA@mail.gmail.com> (raw)
In-Reply-To: <20180524095752.17770-1-liwang@redhat.com>
On Thu, May 24, 2018 at 5:57 AM, Li Wang <liwang@redhat.com> wrote:
> The '/sys/../zswap/stored_pages:' keep raising in zswap test with
> "zswap.max_pool_percent=0" parameter. But theoretically, it should
> not compress or store pages any more since there is no space for
> compressed pool.
>
> Reproduce steps:
>
> 1. Boot kernel with "zswap.enabled=1 zswap.max_pool_percent=17"
> 2. Set the max_pool_percent to 0
> # echo 0 > /sys/module/zswap/parameters/max_pool_percent
> Confirm this parameter works fine
> # cat /sys/kernel/debug/zswap/pool_total_size
> 0
> 3. Do memory stress test to see if some pages have been compressed
> # stress --vm 1 --vm-bytes $mem_available"M" --timeout 60s
> Watching the 'stored_pages' numbers increasing or not
>
> The root cause is:
>
> When the zswap_max_pool_percent is set to 0 via kernel parameter, the zswap_is_full()
> will always return true to shrink the pool size by zswap_shrink(). If the pool size
> has been shrinked a little success, zswap will do compress/store pages again. Then we
> get fails on that as above.
special casing 0% doesn't make a lot of sense to me, and I'm not
entirely sure what exactly you are trying to fix here.
however, zswap does currently do a zswap_is_full() check, and then if
it's able to reclaim a page happily proceeds to store another page,
without re-checking zswap_is_full(). If you're trying to fix that,
then I would ack a patch that adds a second zswap_is_full() check
after zswap_shrink() to make sure it's now under the max_pool_percent
(or somehow otherwise fixes that behavior).
>
> Signed-off-by: Li Wang <liwang@redhat.com>
> Cc: Seth Jennings <sjenning@redhat.com>
> Cc: Dan Streetman <ddstreet@ieee.org>
> Cc: Huang Ying <huang.ying.caritas@gmail.com>
> Cc: Yu Zhao <yuzhao@google.com>
> ---
> mm/zswap.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/mm/zswap.c b/mm/zswap.c
> index 61a5c41..2b537bb 100644
> --- a/mm/zswap.c
> +++ b/mm/zswap.c
> @@ -1007,6 +1007,11 @@ static int zswap_frontswap_store(unsigned type, pgoff_t offset,
> u8 *src, *dst;
> struct zswap_header zhdr = { .swpentry = swp_entry(type, offset) };
>
> + if (!zswap_max_pool_percent) {
> + ret = -ENOMEM;
> + goto reject;
> + }
> +
> /* THP isn't supported */
> if (PageTransHuge(page)) {
> ret = -EINVAL;
> --
> 2.9.5
>
next prev parent reply other threads:[~2018-05-29 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 9:57 Li Wang
2018-05-29 21:14 ` Dan Streetman [this message]
2018-05-30 2:57 ` Li Wang
2018-05-30 8:52 ` Dan Streetman
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=CALZtONA4y+7vzUr2xPa8ZbwCczjJV9EMCOXaCsE94DdfGbrmtA@mail.gmail.com \
--to=ddstreet@ieee.org \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--cc=sjenning@redhat.com \
--cc=yuzhao@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