Re: [PATCH 4/6] mm/page_owner: introduce split_page_owner and replace manual handling

2016-05-10 Thread Vlastimil Babka
On 05/03/2016 07:23 AM, js1...@gmail.com wrote: From: Joonsoo Kim split_page() calls set_page_owner() to set up page_owner to each pages. But, it has a drawback that head page and the others have different stacktrace because callsite of set_page_owner() is slightly

Re: [PATCH 4/6] mm/page_owner: introduce split_page_owner and replace manual handling

2016-05-10 Thread Vlastimil Babka
On 05/03/2016 07:23 AM, js1...@gmail.com wrote: From: Joonsoo Kim split_page() calls set_page_owner() to set up page_owner to each pages. But, it has a drawback that head page and the others have different stacktrace because callsite of set_page_owner() is slightly differnt. To avoid this

[PATCH 4/6] mm/page_owner: introduce split_page_owner and replace manual handling

2016-05-02 Thread js1304
From: Joonsoo Kim split_page() calls set_page_owner() to set up page_owner to each pages. But, it has a drawback that head page and the others have different stacktrace because callsite of set_page_owner() is slightly differnt. To avoid this problem, this patch copies

[PATCH 4/6] mm/page_owner: introduce split_page_owner and replace manual handling

2016-05-02 Thread js1304
From: Joonsoo Kim split_page() calls set_page_owner() to set up page_owner to each pages. But, it has a drawback that head page and the others have different stacktrace because callsite of set_page_owner() is slightly differnt. To avoid this problem, this patch copies head page's page_owner to