[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 6 Jun 2019 02:23:56 +0200
From: Vitaly Wool <vitalywool@...il.com>
To: Shakeel Butt <shakeelb@...gle.com>
Cc: Hui Zhu <teawaterz@...ux.alibaba.com>,
Dan Streetman <ddstreet@...e.org>,
Minchan Kim <minchan@...nel.org>,
Nitin Gupta <ngupta@...are.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Seth Jennings <sjenning@...hat.com>,
Linux MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V3 1/2] zpool: Add malloc_support_movable to zpool_driver
Hi Shakeel,
On Wed, Jun 5, 2019 at 6:31 PM Shakeel Butt <shakeelb@...gle.com> wrote:
>
> On Wed, Jun 5, 2019 at 3:06 AM Hui Zhu <teawaterz@...ux.alibaba.com> wrote:
> >
> > As a zpool_driver, zsmalloc can allocate movable memory because it
> > support migate pages.
> > But zbud and z3fold cannot allocate movable memory.
> >
>
> Cc: Vitaly
thanks for looping me in :)
> It seems like z3fold does support page migration but z3fold's malloc
> is rejecting __GFP_HIGHMEM. Vitaly, is there a reason to keep
> rejecting __GFP_HIGHMEM after 1f862989b04a ("mm/z3fold.c: support page
> migration").
No; I don't think I see a reason to keep that part. You are very
welcome to submit a patch, or otherwise I can do it when I'm done with
the patches that are already in the pipeline.
Thanks,
Vitaly
Powered by blists - more mailing lists