From: Andrew Morton <akpm@linux-foundation.org>
To: js1304@gmail.com
Cc: Michal Nazarewicz <mina86@mina86.com>,
Minchan Kim <minchan@kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Vlastimil Babka <vbabka@suse.cz>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v3 1/2] mm: introduce page reference manipulation functions
Date: Tue, 23 Feb 2016 15:32:44 -0800 [thread overview]
Message-ID: <20160223153244.83a5c3ca430c4248a4a34cc0@linux-foundation.org> (raw)
In-Reply-To: <1456212078-22732-1-git-send-email-iamjoonsoo.kim@lge.com>
On Tue, 23 Feb 2016 16:21:17 +0900 js1304@gmail.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> 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
> of CMA allocation failure. CMA allocation should be guaranteed to succeed
> so finding offending place is really important.
>
> In this patch, call sites where page reference is manipulated are converted
> to introduced wrapper function. This is preparation step to add tracepoint
> to each page reference manipulation function. With this facility, we can
> easily find reason of CMA allocation failure. There is no functional change
> in this patch.
>
> ...
>
> --- a/arch/mips/mm/gup.c
> +++ b/arch/mips/mm/gup.c
> @@ -64,7 +64,7 @@ static inline void get_head_page_multiple(struct page *page, int nr)
> {
> VM_BUG_ON(page != compound_head(page));
> VM_BUG_ON(page_count(page) == 0);
> - atomic_add(nr, &page->_count);
> + page_ref_add(page, nr);
Seems reasonable. Those open-coded refcount manipulations have always
bugged me.
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.
After that pass is completed I suggest we rename page._count to
something else (page.ref_count_dont_use_this_directly_you_dope?). That
way, any attempts to later add direct page._count references will
hopefully break, alerting the programmer to the new regime.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-02-23 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 7:21 [PATCH v3 1/2] mm: introduce page reference manipulation functions js1304-Re5JQEeQqe8AvxtiuMwx3w
2016-02-23 7:21 ` [PATCH v3 2/2] mm/page_ref: add tracepoint to track down page reference manipulation js1304
2016-02-23 23:32 ` Andrew Morton [this message]
[not found] ` <20160223153244.83a5c3ca430c4248a4a34cc0-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2016-02-25 0:34 ` [PATCH v3 1/2] mm: introduce page reference manipulation functions Joonsoo Kim
2016-02-25 1:53 ` Andrew Morton
2016-02-25 2:11 ` Joonsoo Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160223153244.83a5c3ca430c4248a4a34cc0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).