Received-SPF: pass (google.com: domain of linux-kernel+bounces-173719-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Precedence: bulk
MIME-Version: 1.0
References: <20240508171359.1545744-1-usamaarif642@gmail.com>
In-Reply-To: <20240508171359.1545744-1-usamaarif642@gmail.com>
From: Nhat Pham <nphamcs@gmail.com>
Date: Wed, 8 May 2024 11:41:50 -0700
Message-ID: <CAKEwX=MhxjUsOq+W2Tf1fdc5O-oyPUBdsct1-Df8VQf8-Q2TuQ@mail.gmail.com>
Subject: Re: [PATCH v5] selftests: cgroup: add tests to verify the zswap
 writeback path
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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, May 8, 2024 at 10:14=E2=80=AFAM 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>