[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKEwX=Ok3g0Cm7dDgGJPpMBGWukTHFy2389Yc5_2WqzNd4Nmag@mail.gmail.com>
Date: Thu, 15 Aug 2024 12:10:31 -0700
From: Nhat Pham <nphamcs@...il.com>
To: Mike Yuan <me@...dnzj.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, cgroups@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, Muchun Song <muchun.song@...ux.dev>,
Shakeel Butt <shakeel.butt@...ux.dev>, Roman Gushchin <roman.gushchin@...ux.dev>,
Michal Hocko <mhocko@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
Yosry Ahmed <yosryahmed@...gle.com>
Subject: Re: [PATCH] mm/memcontrol: respect zswap.writeback setting from
parent cg too
On Thu, Aug 15, 2024 at 11:39 AM Mike Yuan <me@...dnzj.com> wrote:
>
>
> Hmm, I tried to, but the test_zswap_writeback_enabled and
> test_zswap_writeback_disabled tests in the current tree already
> fail for me... Should I still add new test cases under this
> circumstance?
Hmm interesting. We need to fix it - could you forward me the details
of the failure mode?
But yeah, for now let's skip the selftest. Could you send a fixlet or
a follow up patch to update the documentation :)
Powered by blists - more mailing lists