Re: [PATCH v5 09/12] zsmalloc: separate free_zspage from putback_zspage

2016-05-15 Thread Sergey Senozhatsky
On (05/09/16 11:20), Minchan Kim wrote: > Currently, putback_zspage does free zspage under class->lock > if fullness become ZS_EMPTY but it makes trouble to implement > locking scheme for new zspage migration. > So, this patch is to separate free_zspage from putback_zspage > and free zspage out of

Re: [PATCH v5 09/12] zsmalloc: separate free_zspage from putback_zspage

2016-05-15 Thread Sergey Senozhatsky
On (05/09/16 11:20), Minchan Kim wrote: > Currently, putback_zspage does free zspage under class->lock > if fullness become ZS_EMPTY but it makes trouble to implement > locking scheme for new zspage migration. > So, this patch is to separate free_zspage from putback_zspage > and free zspage out of

[PATCH v5 09/12] zsmalloc: separate free_zspage from putback_zspage

2016-05-08 Thread Minchan Kim
Currently, putback_zspage does free zspage under class->lock if fullness become ZS_EMPTY but it makes trouble to implement locking scheme for new zspage migration. So, this patch is to separate free_zspage from putback_zspage and free zspage out of class->lock which is preparation for zspage

[PATCH v5 09/12] zsmalloc: separate free_zspage from putback_zspage

2016-05-08 Thread Minchan Kim
Currently, putback_zspage does free zspage under class->lock if fullness become ZS_EMPTY but it makes trouble to implement locking scheme for new zspage migration. So, this patch is to separate free_zspage from putback_zspage and free zspage out of class->lock which is preparation for zspage