Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-17 Thread Joonsoo Kim
On Thu, Jun 16, 2016 at 07:09:32PM +0900, Minchan Kim wrote: > On Thu, Jun 16, 2016 at 05:42:11PM +0900, Sergey Senozhatsky wrote: > > On (06/16/16 15:47), Minchan Kim wrote: > > > > [..] > > > > > > this is what I'm getting with the [zsmalloc: keep first object > > > > > > offset in struct page]

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-16 Thread Minchan Kim
On Thu, Jun 16, 2016 at 05:42:11PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 15:47), Minchan Kim wrote: > > > [..] > > > > > this is what I'm getting with the [zsmalloc: keep first object offset > > > > > in struct page] > > > > > applied: "count:0 mapcount:-127". which may be not related

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-16 Thread Sergey Senozhatsky
On (06/16/16 15:47), Minchan Kim wrote: > > [..] > > > > this is what I'm getting with the [zsmalloc: keep first object offset > > > > in struct page] > > > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc > > > > at this point. > > > > > > > > kernel: BUG: Bad page

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-16 Thread Minchan Kim
On Thu, Jun 16, 2016 at 02:22:09PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 13:47), Minchan Kim wrote: > [..] > > > this is what I'm getting with the [zsmalloc: keep first object offset in > > > struct page] > > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc > >

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-15 Thread Sergey Senozhatsky
On (06/16/16 13:47), Minchan Kim wrote: [..] > > this is what I'm getting with the [zsmalloc: keep first object offset in > > struct page] > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc at > > this point. > > > > kernel: BUG: Bad page state in process khugepaged

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-15 Thread Minchan Kim
On Thu, Jun 16, 2016 at 01:23:43PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 11:58), Minchan Kim wrote: > [..] > > RAX: 2065676162726166 so rax is totally garbage, I think. > > It means obj_to_head returns garbage because get_first_obj_offset is > > utter crab because (page_idx /

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-15 Thread Sergey Senozhatsky
On (06/16/16 11:58), Minchan Kim wrote: [..] > RAX: 2065676162726166 so rax is totally garbage, I think. > It means obj_to_head returns garbage because get_first_obj_offset is > utter crab because (page_idx / class->pages_per_zspage) was totally > wrong. > > >

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-15 Thread Minchan Kim
On Thu, Jun 16, 2016 at 11:48:27AM +0900, Sergey Senozhatsky wrote: > Hi, > > On (06/16/16 08:12), Minchan Kim wrote: > > > [ 315.146533] kasan: CONFIG_KASAN_INLINE enabled > > > [ 315.146538] kasan: GPF could be caused by NULL-ptr deref or user > > > memory access > > > [ 315.146546] general

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-15 Thread Sergey Senozhatsky
Hi, On (06/16/16 08:12), Minchan Kim wrote: > > [ 315.146533] kasan: CONFIG_KASAN_INLINE enabled > > [ 315.146538] kasan: GPF could be caused by NULL-ptr deref or user memory > > access > > [ 315.146546] general protection fault: [#1] PREEMPT SMP KASAN > > [ 315.146576] Modules linked

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-15 Thread Minchan Kim
Hi Sergey, On Wed, Jun 15, 2016 at 04:59:09PM +0900, Sergey Senozhatsky wrote: > Hello Minchan, > > -next 4.7.0-rc3-next-20160614 > > > [ 315.146533] kasan: CONFIG_KASAN_INLINE enabled > [ 315.146538] kasan: GPF could be caused by NULL-ptr deref or user memory > access > [ 315.146546]

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-15 Thread Sergey Senozhatsky
Hello Minchan, -next 4.7.0-rc3-next-20160614 [ 315.146533] kasan: CONFIG_KASAN_INLINE enabled [ 315.146538] kasan: GPF could be caused by NULL-ptr deref or user memory access [ 315.146546] general protection fault: [#1] PREEMPT SMP KASAN [ 315.146576] Modules linked in: lzo zram

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-01 Thread Minchan Kim
On Wed, Jun 01, 2016 at 02:41:51PM -0700, Andrew Morton wrote: > On Wed, 1 Jun 2016 08:21:09 +0900 Minchan Kim wrote: > > > Recently, I got many reports about perfermance degradation in embedded > > system(Android mobile phone, webOS TV and so on) and easy fork fail. > > >

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-01 Thread Daniel Vetter
On Wed, Jun 01, 2016 at 02:41:51PM -0700, Andrew Morton wrote: > On Wed, 1 Jun 2016 08:21:09 +0900 Minchan Kim wrote: > > > Recently, I got many reports about perfermance degradation in embedded > > system(Android mobile phone, webOS TV and so on) and easy fork fail. > > >

Re: [PATCH v7 00/12] Support non-lru page migration

2016-06-01 Thread Andrew Morton
On Wed, 1 Jun 2016 08:21:09 +0900 Minchan Kim wrote: > Recently, I got many reports about perfermance degradation in embedded > system(Android mobile phone, webOS TV and so on) and easy fork fail. > > The problem was fragmentation caused by zram and GPU driver mainly. >

[PATCH v7 00/12] Support non-lru page migration

2016-05-31 Thread Minchan Kim
Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be