Re: [PATCH v2 3/8] mm/zsmalloc: take obj index back from find_alloced_obj

From: Minchan Kim
Date: Tue Jul 05 2016 - 22:39:46 EST

Next message: Minchan Kim: "Re: [PATCH v2 5/8] mm/zsmalloc: avoid calculate max objects of zspage twice"
Previous message: Xiao Guangrong: "Re: [PATCH 0/2] KVM: MMU: support VMAs that got remap_pfn_range-ed"
In reply to: Sergey Senozhatsky: "Re: [PATCH v2 3/8] mm/zsmalloc: take obj index back from find_alloced_obj"
Next in thread: Ganesh Mahendran: "[PATCH v2 4/8] mm/zsmalloc: use class->objs_per_zspage to get num of max objects"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Jul 04, 2016 at 02:49:54PM +0800, Ganesh Mahendran wrote:
> the obj index value should be updated after return from
> find_alloced_obj() to avoid CPU buring caused by unnecessary
> object scanning.
>
> Signed-off-by: Ganesh Mahendran <opensource.ganesh@xxxxxxxxx>
Acked-by: Minchan Kim <minchan@xxxxxxxxxx>

Next message: Minchan Kim: "Re: [PATCH v2 5/8] mm/zsmalloc: avoid calculate max objects of zspage twice"
Previous message: Xiao Guangrong: "Re: [PATCH 0/2] KVM: MMU: support VMAs that got remap_pfn_range-ed"
In reply to: Sergey Senozhatsky: "Re: [PATCH v2 3/8] mm/zsmalloc: take obj index back from find_alloced_obj"
Next in thread: Ganesh Mahendran: "[PATCH v2 4/8] mm/zsmalloc: use class->objs_per_zspage to get num of max objects"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]