[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160225021134.GA14784@js1304-P5Q-DELUXE>
Date: Thu, 25 Feb 2016 11:11:34 +0900
From: Joonsoo Kim <iamjoonsoo.kim@....com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Michal Nazarewicz <mina86@...a86.com>,
Minchan Kim <minchan@...nel.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Vlastimil Babka <vbabka@...e.cz>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Steven Rostedt <rostedt@...dmis.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH v3 1/2] mm: introduce page reference manipulation
functions
On Wed, Feb 24, 2016 at 05:53:33PM -0800, Andrew Morton wrote:
> On Thu, 25 Feb 2016 09:34:55 +0900 Joonsoo Kim <iamjoonsoo.kim@....com> 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 second pass to complete the conversion.
> >
> > In fact, the patch doesn't change direct ->_count reference for
> > *read*. That's the reason that it is surprisingly OK at present.
> >
> > It's a good idea to change direct ->_count reference even for read.
> > How about changing it in rc2 after mering this patch in rc1?
>
> Sounds fair enough.
>
> Although I'm counting only 11 such sites so perhaps we just go ahead
> and do it?
Okay. It's less than I thought. I will do it soon.
Thanks.
Powered by blists - more mailing lists