Re: [RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object.

2017-03-29 Thread Yisheng Xie
Hi Sergey, Thanks for your comment! On 2017/3/29 14:42, Sergey Senozhatsky wrote: > On (03/29/17 09:20), Minchan Kim wrote: >> Hello, >> >> On Tue, Mar 28, 2017 at 03:20:22PM +0800, Yisheng Xie wrote: >>> Hi, all, >>> >>> We had backport the no-lru migration to linux-4.1, meanwhile change the >>>

Re: [RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object.

2017-03-29 Thread Yisheng Xie
Hi Minchan, Thanks for your comment! On 2017/3/29 8:20, Minchan Kim wrote: > Hello, > > On Tue, Mar 28, 2017 at 03:20:22PM +0800, Yisheng Xie wrote: >> Hi, all, >> >> We had backport the no-lru migration to linux-4.1, meanwhile change the >> ZS_MAX_ZSPAGE_ORDER to 3. Then we met a BUG_ON(!page[1]

Re: [RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object.

2017-03-28 Thread Sergey Senozhatsky
On (03/29/17 09:20), Minchan Kim wrote: > Hello, > > On Tue, Mar 28, 2017 at 03:20:22PM +0800, Yisheng Xie wrote: > > Hi, all, > > > > We had backport the no-lru migration to linux-4.1, meanwhile change the > > ZS_MAX_ZSPAGE_ORDER to 3. Then we met a BUG_ON(!page[1]). > > Hmm, I don't know how y

Re: [RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object.

2017-03-28 Thread Minchan Kim
Hello, On Tue, Mar 28, 2017 at 03:20:22PM +0800, Yisheng Xie wrote: > Hi, all, > > We had backport the no-lru migration to linux-4.1, meanwhile change the > ZS_MAX_ZSPAGE_ORDER to 3. Then we met a BUG_ON(!page[1]). Hmm, I don't know how you backported. There isn't any problem with default ZS_MA

[RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object.

2017-03-28 Thread Yisheng Xie
Hi, all, We had backport the no-lru migration to linux-4.1, meanwhile change the ZS_MAX_ZSPAGE_ORDER to 3. Then we met a BUG_ON(!page[1]). It rarely happen, and presently, what I get is: [6823.316528s]obj=a160701f, obj_idx=15, class{size:2176,objs_per_zspage:15,pages_per_zspage:8} [...] [6823.31