[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y8WYvmNdSkk23nbO@monkey>
Date: Mon, 16 Jan 2023 10:34:38 -0800
From: Mike Kravetz <mike.kravetz@...cle.com>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan@...nel.org>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCHv2 0/4] zsmalloc: make zspage chain size configurable
On 01/16/23 12:15, Sergey Senozhatsky wrote:
> On (23/01/09 12:38), Sergey Senozhatsky wrote:
> > This turns hard coded limit on maximum number of physical
> > pages per-zspage into a config option. It also increases the default
> > limit from 4 to 8.
> >
> > Sergey Senozhatsky (4):
> > zsmalloc: rework zspage chain size selection
> > zsmalloc: skip chain size calculation for pow_of_2 classes
> > zsmalloc: make zspage chain size configurable
> > zsmalloc: set default zspage chain size to 8
> >
> > Documentation/mm/zsmalloc.rst | 168 ++++++++++++++++++++++++++++++++++
> > mm/Kconfig | 19 ++++
> > mm/zsmalloc.c | 72 +++++----------
> > 3 files changed, 212 insertions(+), 47 deletions(-)
>
> Andrew,
>
> Can you please drop this series? We have two fixup patches (hppa64 build
> failure and isolated bit-field overflow reported by Mike) for this series
> and at this point I probably want to send out v3 with all fixups squashed.
>
> Mike, would that be OK with you if I squash ->isolated fixup?
I'm OK with however you want to address. Thanks!
--
Mike Kravetz
Powered by blists - more mailing lists