[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA_GA1da3jkOO9Y3+L6_DMmiH8wsbJJ-xcUxUK_Gh2SYPPbjoA@mail.gmail.com>
Date: Thu, 15 Aug 2013 08:18:46 +0800
From: Bob Liu <lliubbo@...il.com>
To: Minchan Kim <minchan@...nel.org>
Cc: Luigi Semenzato <semenzato@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Jens Axboe <axboe@...nel.dk>,
Seth Jennings <sjenning@...ux.vnet.ibm.com>,
Nitin Gupta <ngupta@...are.org>,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Linux-Kernel <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Mel Gorman <mgorman@...e.de>
Subject: Re: [PATCH v6 0/5] zram/zsmalloc promotion
On Thu, Aug 15, 2013 at 12:17 AM, Minchan Kim <minchan@...nel.org> wrote:
> Hi Luigi,
>
> On Wed, Aug 14, 2013 at 08:53:31AM -0700, Luigi Semenzato wrote:
>> During earlier discussions of zswap there was a plan to make it work
>> with zsmalloc as an option instead of zbud. Does zbud work for
>
> AFAIR, it was not an optoin but zsmalloc was must but there were
> several objections because zswap's notable feature is to dump
> compressed object to real swap storage. For that, zswap needs to
> store bounded objects in a zpage so that dumping could be bounded, too.
> Otherwise, it could encounter OOM easily.
>
AFAIR, the next step of zswap should be have a modular allocation layer so that
users can choose zsmalloc or zbud to use.
Seth?
--
Regards,
--Bob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists