[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACSyD1MKWj9t=q7aWfiqZUT96sVO=9bHJ5SR2kvBGO6t88jgNA@mail.gmail.com>
Date: Thu, 16 Nov 2023 12:23:17 +0800
From: 贺中坤 <hezhongkun.hzk@...edance.com>
To: Yosry Ahmed <yosryahmed@...gle.com>
Cc: akpm@...ux-foundation.org, hannes@...xchg.org, nphamcs@...il.com,
sjenning@...hat.com, ddstreet@...e.org, vitaly.wool@...sulko.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Ying <ying.huang@...el.com>
Subject: Re: [External] Re: [PATCH] mm:zswap: fix zswap entry reclamation
failure in two scenarios
On Thu, Nov 16, 2023 at 12:10 PM Yosry Ahmed <yosryahmed@...gle.com> wrote:
>
> It can be enabled at runtime, or enabled by default by using
> CONFIG_ZSWAP_EXCLUSIVE_LOADS_DEFAULT_ON.
>
Yes, I see it in the doc. Thanks.
>
>
> The reason I added it behind runtime and config knobs is to preserve
> the existing behavior in case someone depends on it. At Google, we
> have been using exclusive loads for a long time. If other users of
> zswap agree to make this the default behavior or make it the only way
> to do zswap loads I don't have a problem with it.
>
Got it. Thanks for your feedback.
Powered by blists - more mailing lists