Re: [PATCH v3 1/2] mm: introduce page reference manipulation functions

2016-02-24 Thread Joonsoo Kim
On Wed, Feb 24, 2016 at 05:53:33PM -0800, Andrew Morton wrote: > On Thu, 25 Feb 2016 09:34:55 +0900 Joonsoo Kim wrote: > > > > > > > The patches will be a bit of a pain to maintain but surprisingly they > > > apply OK at present. It's possible that by the time they hit upstream, > > > some dire

Re: [PATCH v3 1/2] mm: introduce page reference manipulation functions

2016-02-24 Thread Andrew Morton
On Thu, 25 Feb 2016 09:34:55 +0900 Joonsoo Kim wrote: > > > > The patches will be a bit of a pain to maintain but surprisingly they > > apply OK at present. It's possible that by the time they hit upstream, > > some direct ->_count references will still be present and it will > > require a seco

Re: [PATCH v3 1/2] mm: introduce page reference manipulation functions

2016-02-24 Thread Joonsoo Kim
On Tue, Feb 23, 2016 at 03:32:44PM -0800, Andrew Morton wrote: > On Tue, 23 Feb 2016 16:21:17 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > Success of CMA allocation largely depends on success of migration > > and key factor of it is page reference count. Until now, page referenc

Re: [PATCH v3 1/2] mm: introduce page reference manipulation functions

2016-02-23 Thread Andrew Morton
On Tue, 23 Feb 2016 16:21:17 +0900 js1...@gmail.com wrote: > From: Joonsoo Kim > > Success of CMA allocation largely depends on success of migration > and key factor of it is page reference count. Until now, page reference > is manipulated by direct calling atomic functions so we cannot follow u

[PATCH v3 1/2] mm: introduce page reference manipulation functions

2016-02-22 Thread js1304
From: Joonsoo Kim Success of CMA allocation largely depends on success of migration and key factor of it is page reference count. Until now, page reference is manipulated by direct calling atomic functions so we cannot follow up who and where manipulate it. Then, it is hard to find actual reason