On Fri, 13 Nov 2015 11:23:47 +0900 Joonsoo Kim <js1...@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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
