[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160705011812.GC459@swordfish>
Date: Tue, 5 Jul 2016 10:18:12 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Ganesh Mahendran <opensource.ganesh@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
akpm@...ux-foundation.org, minchan@...nel.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 (07/04/16 14:49), 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>
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
-ss
Powered by blists - more mailing lists