[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160706024119.GE13566@bbox>
Date: Wed, 6 Jul 2016 11:41:19 +0900
From: Minchan Kim <minchan@...nel.org>
To: Ganesh Mahendran <opensource.ganesh@...il.com>
CC: <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<akpm@...ux-foundation.org>, <ngupta@...are.org>,
<sergey.senozhatsky.work@...il.com>, <rostedt@...dmis.org>,
<mingo@...hat.com>
Subject: Re: [PATCH v2 5/8] mm/zsmalloc: avoid calculate max objects of
zspage twice
On Mon, Jul 04, 2016 at 02:49:56PM +0800, Ganesh Mahendran wrote:
> Currently, if a class can not be merged, the max objects of zspage
> in that class may be calculated twice.
>
> This patch calculate max objects of zspage at the begin, and pass
> the value to can_merge() to decide whether the class can be merged.
>
> Also this patch remove function get_maxobj_per_zspage(), as there
> is no other place to call this funtion.
>
> Signed-off-by: Ganesh Mahendran <opensource.ganesh@...il.com>
Acked-by: Minchan Kim <minchan@...nel.org>
Powered by blists - more mailing lists