From: Andrew Morton <akpm@linux-foundation.org>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Michal Nazarewicz <mina86@mina86.com>,
Minchan Kim <minchan@kernel.org>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
Date: Thu, 19 Nov 2015 15:34:11 -0800 [thread overview]
Message-ID: <20151119153411.6215be690f75f70b3fa84766@linux-foundation.org> (raw)
In-Reply-To: <1447381428-12445-2-git-send-email-iamjoonsoo.kim@lge.com>
On Fri, 13 Nov 2015 11:23:47 +0900 Joonsoo Kim <js1304@gmail.com> wrote:
> cma allocation should be guranteeded to succeed, but, sometimes,
> it could be failed in current implementation. To track down
> the problem, we need to know which page is problematic and
> this new tracepoint will report it.
akpm3:/usr/src/25> size mm/page_isolation.o
text data bss dec hex filename
2972 112 1096 4180 1054 mm/page_isolation.o-before
4608 570 1840 7018 1b6a mm/page_isolation.o-after
This seems an excessive amount of bloat for one little tracepoint. Is
this expected and normal (and acceptable)?
--
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:[~2015-11-19 23:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 2:23 [PATCH 1/3] mm/page_isolation: return last tested pfn rather than failure indicator Joonsoo Kim
2015-11-13 2:23 ` [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated Joonsoo Kim
2015-11-13 22:51 ` David Rientjes
2015-11-19 23:34 ` Andrew Morton [this message]
2015-11-20 6:21 ` Joonsoo Kim
2015-11-24 14:57 ` Vlastimil Babka
2015-11-13 2:23 ` [PATCH 3/3] mm/cma: always check which page cause allocation failure Joonsoo Kim
2015-11-24 15:27 ` Vlastimil Babka
2015-11-25 2:39 ` Joonsoo Kim
2015-11-25 5:32 ` [PATCH v2] " Joonsoo Kim
2015-11-25 10:45 ` Vlastimil Babka
2015-11-24 14:57 ` [PATCH 1/3] mm/page_isolation: return last tested pfn rather than failure indicator Vlastimil Babka
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=20151119153411.6215be690f75f70b3fa84766@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
/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).