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
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
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.
>
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.
>
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(),
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(),
6 matches
Mail list logo