From: Nhat Pham <nphamcs@gmail.com>
To: Usama Arif <usamaarif642@gmail.com>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
yosryahmed@google.com, chengming.zhou@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH v5] selftests: cgroup: add tests to verify the zswap writeback path
Date: Wed, 8 May 2024 11:41:50 -0700 [thread overview]
Message-ID: <CAKEwX=MhxjUsOq+W2Tf1fdc5O-oyPUBdsct1-Df8VQf8-Q2TuQ@mail.gmail.com> (raw)
In-Reply-To: <20240508171359.1545744-1-usamaarif642@gmail.com>
On Wed, May 8, 2024 at 10:14 AM Usama Arif <usamaarif642@gmail.com> wrote:
>
> Attempt writeback with the below steps and check using
> memory.stat.zswpwb if zswap writeback occurred:
> 1. Allocate memory.
> 2. Reclaim memory equal to the amount that was allocated in step 1.
> This will move it into zswap.
> 3. Save current zswap usage.
> 4. Move the memory allocated in step 1 back in from zswap.
> 5. Set zswap.max to half the amount that was recorded in step 3.
> 6. Attempt to reclaim memory equal to the amount that was allocated,
> this will either trigger writeback if it's enabled, or reclamation
> will fail if writeback is disabled as there isn't enough zswap
> space.
>
> Suggested-by: Nhat Pham <nphamcs@gmail.com>
> Signed-off-by: Usama Arif <usamaarif642@gmail.com>
> Acked-by: Yosry Ahmed <yosryahmed@google.com>
Thanks for adding this test, Usama!
Acked-by: Nhat Pham <nphamcs@gmail.com>
prev parent reply other threads:[~2024-05-08 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 17:13 [PATCH v5] selftests: cgroup: add tests to verify the zswap writeback path Usama Arif
2024-05-08 18:41 ` Nhat Pham [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='CAKEwX=MhxjUsOq+W2Tf1fdc5O-oyPUBdsct1-Df8VQf8-Q2TuQ@mail.gmail.com' \
--to=nphamcs@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=usamaarif642@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).