[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1427216312.2515.46.camel@j-VirtualBox>
Date: Tue, 24 Mar 2015 09:58:32 -0700
From: Jason Low <jason.low2@...com>
To: Christian Borntraeger <borntraeger@...ibm.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
cgroups@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...e.cz>,
Christoph Lameter <cl@...ux.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Aswin Chandramouleeswaran <aswin@...com>,
Mel Gorman <mgorman@...e.de>, Hugh Dickins <hughd@...gle.com>,
Minchan Kim <minchan@...nel.org>,
Davidlohr Bueso <dave@...olabs.net>,
Rik van Riel <riel@...hat.com>, jason.low2@...com
Subject: Re: [PATCH] mm: Remove usages of ACCESS_ONCE
On Tue, 2015-03-24 at 15:42 +0100, Christian Borntraeger wrote:
> Am 23.03.2015 um 23:44 schrieb Jason Low:
> > Commit 38c5ce936a08 converted ACCESS_ONCE usage in gup_pmd_range() to
> > READ_ONCE, since ACCESS_ONCE doesn't work reliably on non-scalar types.
> >
> > This patch removes the rest of the usages of ACCESS_ONCE, and use
> > READ_ONCE for the read accesses. This also makes things cleaner,
> > instead of using separate/multiple sets of APIs.
> >
> > Signed-off-by: Jason Low <jason.low2@...com>
>
> Reviewed-by: Christian Borntraeger <borntraeger@...ibm.com>
Thanks.
> one remark or question:
>
> > - anon_mapping = (unsigned long) ACCESS_ONCE(page->mapping);
> > + anon_mapping = (unsigned long)READ_ONCE(page->mapping);
>
> Were the white space changes intentional? IIRC checkpatch does prefer
> it your way and you have changed several places - so I assume yes.
Yeah, those changes were intentional.
I thought that this was more of the standard style to do casting, so I
made those changes as well.
> Either way, its probably fine to change that along.
Okay, I'll assume that this is fine for now unless something thinks this
shouldn't be part of the patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists