[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230323075927.GB20444@lst.de>
Date: Thu, 23 Mar 2023 08:59:27 +0100
From: Christoph Hellwig <hch@....de>
To: Vitaly Wool <vitaly.wool@...sulko.com>
Cc: Liu Shixin <liushixin2@...wei.com>,
Seth Jennings <sjenning@...hat.com>,
Dan Streetman <ddstreet@...e.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Nathan Chancellor <nathan@...nel.org>,
Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH -next v6 2/2] mm/zswap: delay the initializaton of zswap
On Wed, Mar 22, 2023 at 06:17:12PM +0100, Vitaly Wool wrote:
> On Wed, Mar 22, 2023 at 10:30 AM Liu Shixin <liushixin2@...wei.com> wrote:
> >
> > Since some users may not use zswap, the zswap_pool is wasted. Save memory
> > by delaying the initialization of zswap until enabled.
>
> To be honest, I'm not a huge fan of this. Would enabling zswap module
> build instead solve your problem?
making zswap build modular would be a mess. It is core MM infrastructure
and now we'd need to start dealing with adding and removing it at
runtime as well as module refcounting.
Powered by blists - more mailing lists