Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-06 Thread Daniel Vetter
On Wed, Mar 06, 2013 at 11:48:36AM +0100, Marek Szyprowski wrote: > Hello, > > On 3/6/2013 9:47 AM, Minchan Kim wrote: > >Hello, > > > >On Tue, Mar 5, 2013 at 3:57 PM, Marek Szyprowski > > wrote: > >> Hello, > >> > >> Contiguous Memory Allocator is very sensitive about migration failures > >> of

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-06 Thread Marek Szyprowski
Hello, On 3/6/2013 9:47 AM, Minchan Kim wrote: Hello, On Tue, Mar 5, 2013 at 3:57 PM, Marek Szyprowski wrote: > Hello, > > Contiguous Memory Allocator is very sensitive about migration failures > of the individual pages. A single page, which causes permanent migration > failure can break

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-06 Thread Minchan Kim
Hello, On Tue, Mar 5, 2013 at 3:57 PM, Marek Szyprowski wrote: > Hello, > > Contiguous Memory Allocator is very sensitive about migration failures > of the individual pages. A single page, which causes permanent migration > failure can break large conitguous allocations and cause the failure of

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-06 Thread Minchan Kim
Hello, On Tue, Mar 5, 2013 at 3:57 PM, Marek Szyprowski m.szyprow...@samsung.com wrote: Hello, Contiguous Memory Allocator is very sensitive about migration failures of the individual pages. A single page, which causes permanent migration failure can break large conitguous allocations and

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-06 Thread Marek Szyprowski
Hello, On 3/6/2013 9:47 AM, Minchan Kim wrote: Hello, On Tue, Mar 5, 2013 at 3:57 PM, Marek Szyprowski m.szyprow...@samsung.com wrote: Hello, Contiguous Memory Allocator is very sensitive about migration failures of the individual pages. A single page, which causes permanent migration

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-06 Thread Daniel Vetter
On Wed, Mar 06, 2013 at 11:48:36AM +0100, Marek Szyprowski wrote: Hello, On 3/6/2013 9:47 AM, Minchan Kim wrote: Hello, On Tue, Mar 5, 2013 at 3:57 PM, Marek Szyprowski m.szyprow...@samsung.com wrote: Hello, Contiguous Memory Allocator is very sensitive about migration failures of

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Yasuaki Ishimatsu
2013/03/05 15:57, Marek Szyprowski wrote: > Hello, > > Contiguous Memory Allocator is very sensitive about migration failures > of the individual pages. A single page, which causes permanent migration > failure can break large conitguous allocations and cause the failure of > a multimedia device

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Daniel Vetter
On Tue, Mar 5, 2013 at 7:57 AM, Marek Szyprowski wrote: > Hello, > > Contiguous Memory Allocator is very sensitive about migration failures > of the individual pages. A single page, which causes permanent migration > failure can break large conitguous allocations and cause the failure of > a

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Arnd Bergmann
On Tuesday 05 March 2013, Marek Szyprowski wrote: > On 3/5/2013 9:50 AM, Arnd Bergmann wrote: > > On Tuesday 05 March 2013, Marek Szyprowski wrote: > > The problem is that the opposite approach is imho easier. I can understand that, yes ;-) > get_user_pages() > is used in quite a lot of places

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Marek Szyprowski
Hello, On 3/5/2013 9:50 AM, Arnd Bergmann wrote: On Tuesday 05 March 2013, Marek Szyprowski wrote: > To solving this issue requires preventing locking of the pages, which > are placed in CMA regions, for a long time. Our idea is to migrate > anonymous page content before locking the page in

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Arnd Bergmann
On Tuesday 05 March 2013, Marek Szyprowski wrote: > To solving this issue requires preventing locking of the pages, which > are placed in CMA regions, for a long time. Our idea is to migrate > anonymous page content before locking the page in get_user_pages(). This > cannot be done automatically,

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Arnd Bergmann
On Tuesday 05 March 2013, Marek Szyprowski wrote: To solving this issue requires preventing locking of the pages, which are placed in CMA regions, for a long time. Our idea is to migrate anonymous page content before locking the page in get_user_pages(). This cannot be done automatically, as

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Marek Szyprowski
Hello, On 3/5/2013 9:50 AM, Arnd Bergmann wrote: On Tuesday 05 March 2013, Marek Szyprowski wrote: To solving this issue requires preventing locking of the pages, which are placed in CMA regions, for a long time. Our idea is to migrate anonymous page content before locking the page in

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Arnd Bergmann
On Tuesday 05 March 2013, Marek Szyprowski wrote: On 3/5/2013 9:50 AM, Arnd Bergmann wrote: On Tuesday 05 March 2013, Marek Szyprowski wrote: The problem is that the opposite approach is imho easier. I can understand that, yes ;-) get_user_pages() is used in quite a lot of places (I was

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Daniel Vetter
On Tue, Mar 5, 2013 at 7:57 AM, Marek Szyprowski m.szyprow...@samsung.com wrote: Hello, Contiguous Memory Allocator is very sensitive about migration failures of the individual pages. A single page, which causes permanent migration failure can break large conitguous allocations and cause the

Re: [RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-05 Thread Yasuaki Ishimatsu
2013/03/05 15:57, Marek Szyprowski wrote: Hello, Contiguous Memory Allocator is very sensitive about migration failures of the individual pages. A single page, which causes permanent migration failure can break large conitguous allocations and cause the failure of a multimedia device

[RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-04 Thread Marek Szyprowski
Hello, Contiguous Memory Allocator is very sensitive about migration failures of the individual pages. A single page, which causes permanent migration failure can break large conitguous allocations and cause the failure of a multimedia device driver. One of the known issues with migration of CMA

[RFC/PATCH 0/5] Contiguous Memory Allocator and get_user_pages()

2013-03-04 Thread Marek Szyprowski
Hello, Contiguous Memory Allocator is very sensitive about migration failures of the individual pages. A single page, which causes permanent migration failure can break large conitguous allocations and cause the failure of a multimedia device driver. One of the known issues with migration of CMA