Re: [PATCH 1/4] mm/zsmalloc: always set movable/highmem flag to the zspage

2017-03-23 Thread Minchan Kim
Hi Joonsoo, On Thu, Mar 23, 2017 at 11:10:23AM +0900, Joonsoo Kim wrote: > On Tue, Mar 21, 2017 at 08:10:05PM +0900, Minchan Kim wrote: > > Hi Joonsoo, > > > > On Thu, Mar 16, 2017 at 11:46:35AM +0900, js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > > > Zspage is always movable and is u

Re: [PATCH 1/4] mm/zsmalloc: always set movable/highmem flag to the zspage

2017-03-22 Thread Joonsoo Kim
On Tue, Mar 21, 2017 at 08:10:05PM +0900, Minchan Kim wrote: > Hi Joonsoo, > > On Thu, Mar 16, 2017 at 11:46:35AM +0900, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Zspage is always movable and is used through zs_map_object() function > > which returns directly accessible pointer that

Re: [PATCH 1/4] mm/zsmalloc: always set movable/highmem flag to the zspage

2017-03-21 Thread Minchan Kim
Hi Joonsoo, On Thu, Mar 16, 2017 at 11:46:35AM +0900, js1...@gmail.com wrote: > From: Joonsoo Kim > > Zspage is always movable and is used through zs_map_object() function > which returns directly accessible pointer that contains content of > zspage. It is independent on the user's allocation fl

[PATCH 1/4] mm/zsmalloc: always set movable/highmem flag to the zspage

2017-03-15 Thread js1304
From: Joonsoo Kim Zspage is always movable and is used through zs_map_object() function which returns directly accessible pointer that contains content of zspage. It is independent on the user's allocation flag. Therefore, it's better to always set movable/highmem flag to the zspage. After that,