[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220827151306.879ec27ea7314a543c5f60f6@linux-foundation.org>
Date: Sat, 27 Aug 2022 15:13:06 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Liu Shixin <liushixin2@...wei.com>
Cc: Seth Jennings <sjenning@...hat.com>,
Dan Streetman <ddstreet@...e.org>,
Vitaly Wool <vitaly.wool@...sulko.com>,
Nathan Chancellor <nathan@...nel.org>,
"Christoph Hellwig" <hch@....de>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: [PATCH -next v3 0/5] Delay the initializaton of zswap
On Sat, 27 Aug 2022 18:45:55 +0800 Liu Shixin <liushixin2@...wei.com> wrote:
> In the initialization of zswap, about 18MB memory will be allocated for
> zswap_pool. Since not all users use zswap, the memory may be wasted. Save
> the memory for these users by delaying the initialization of zswap to
> first enablement.
>
> v2->v3: Fix frontswap_ops NULL reported by Nathan and add init for online
> swap device in backend register.
> v1->v2: Change init_zswap to zswap_init suggested by Andrew.
Thanks. Konrad, could you please take a look for the frontswap
changes?
Powered by blists - more mailing lists