Re: [patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-10-09 Thread Greg KH
On Fri, Oct 07, 2016 at 04:27:49PM +0800, YiPing Xu wrote: > > > On 2016/10/5 2:02, Laura Abbott wrote: > > On 09/30/2016 01:18 AM, Xu YiPing wrote: > > > ion_alloc may get into slow path to get free page, > > > the call stack: > > > > > > __alloc_pages_slowpath > > > ion_page_pool_alloc_pages

Re: [patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-10-09 Thread Greg KH
On Fri, Oct 07, 2016 at 04:27:49PM +0800, YiPing Xu wrote: > > > On 2016/10/5 2:02, Laura Abbott wrote: > > On 09/30/2016 01:18 AM, Xu YiPing wrote: > > > ion_alloc may get into slow path to get free page, > > > the call stack: > > > > > > __alloc_pages_slowpath > > > ion_page_pool_alloc_pages

Re: [patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-10-07 Thread YiPing Xu
On 2016/10/5 2:02, Laura Abbott wrote: On 09/30/2016 01:18 AM, Xu YiPing wrote: ion_alloc may get into slow path to get free page, the call stack: __alloc_pages_slowpath ion_page_pool_alloc_pages alloc_buffer_page ion_system_heap_allocate ion_buffer_create <-- hold ion_device->lock

Re: [patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-10-07 Thread YiPing Xu
On 2016/10/5 2:02, Laura Abbott wrote: On 09/30/2016 01:18 AM, Xu YiPing wrote: ion_alloc may get into slow path to get free page, the call stack: __alloc_pages_slowpath ion_page_pool_alloc_pages alloc_buffer_page ion_system_heap_allocate ion_buffer_create <-- hold ion_device->lock

Re: [patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-10-04 Thread Laura Abbott
On 09/30/2016 01:18 AM, Xu YiPing wrote: ion_alloc may get into slow path to get free page, the call stack: __alloc_pages_slowpath ion_page_pool_alloc_pages alloc_buffer_page ion_system_heap_allocate ion_buffer_create <-- hold ion_device->lock ion_alloc after that, kernel invokes low-memory

Re: [patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-10-04 Thread Laura Abbott
On 09/30/2016 01:18 AM, Xu YiPing wrote: ion_alloc may get into slow path to get free page, the call stack: __alloc_pages_slowpath ion_page_pool_alloc_pages alloc_buffer_page ion_system_heap_allocate ion_buffer_create <-- hold ion_device->lock ion_alloc after that, kernel invokes low-memory

[patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-09-30 Thread Xu YiPing
ion_alloc may get into slow path to get free page, the call stack: __alloc_pages_slowpath ion_page_pool_alloc_pages alloc_buffer_page ion_system_heap_allocate ion_buffer_create <-- hold ion_device->lock ion_alloc after that, kernel invokes low-memory killer to kill some apps in order to free

[patch] staging: ion: use two separate locks for heaps and clients in ion_device

2016-09-30 Thread Xu YiPing
ion_alloc may get into slow path to get free page, the call stack: __alloc_pages_slowpath ion_page_pool_alloc_pages alloc_buffer_page ion_system_heap_allocate ion_buffer_create <-- hold ion_device->lock ion_alloc after that, kernel invokes low-memory killer to kill some apps in order to free