[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220826184328.3bce63050a1f82e9242580df@linux-foundation.org>
Date: Fri, 26 Aug 2022 18:43:28 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: Liu Shixin <liushixin2@...wei.com>,
Seth Jennings <sjenning@...hat.com>,
Dan Streetman <ddstreet@...e.org>,
Vitaly Wool <vitaly.wool@...sulko.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next 2/3] mm/zswap: delay the initializaton of zswap
until the first enablement
On Fri, 26 Aug 2022 13:25:41 -0700 Nathan Chancellor <nathan@...nel.org> wrote:
> Hi Liu,
>
> On Thu, Aug 25, 2022 at 10:20:36PM +0800, Liu Shixin wrote:
> > In the initialization of zswap, about 18MB memory will be allocated for
> > zswap_pool in my machine. 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.
> >
>
> ...
>
> This change is in -next as commit 22100432cf14 ("mm/zswap: delay the
> initializaton of zswap until the first enablement"). I just bisected my
> arm64 test system running Fedora failing to boot due to that commit,
> with the following stack trace:
>
Thanks. Sorry. I dropped the series.
Powered by blists - more mailing lists