Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On 11/13/2015 03:23 AM, Joonsoo Kim 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. Acked-by: Michal Nazarewicz Signed-off-by: Joonsoo Kim Acked-by: Vlastimil Babka -- 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/
Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On 11/13/2015 03:23 AM, Joonsoo Kim 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. Acked-by: Michal NazarewiczSigned-off-by: Joonsoo Kim Acked-by: Vlastimil Babka -- 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/
Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On Thu, Nov 19, 2015 at 03:34:11PM -0800, Andrew Morton wrote: > On Fri, 13 Nov 2015 11:23:47 +0900 Joonsoo Kim 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 >textdata bss dec hex filename >2972 112109641801054 mm/page_isolation.o-before >4608 570184070181b6a mm/page_isolation.o-after > > This seems an excessive amount of bloat for one little tracepoint. Is > this expected and normal (and acceptable)? Hello, I checked bloat on other tracepoints and found that it's normal. It takes 1KB more per tracepoint. Thanks. -- 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/
Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On Fri, 13 Nov 2015 11:23:47 +0900 Joonsoo Kim 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 textdata bss dec hex filename 2972 112109641801054 mm/page_isolation.o-before 4608 570184070181b6a 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/
Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On Fri, 13 Nov 2015 11:23:47 +0900 Joonsoo Kimwrote: > 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 textdata bss dec hex filename 2972 112109641801054 mm/page_isolation.o-before 4608 570184070181b6a 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/
Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On Thu, Nov 19, 2015 at 03:34:11PM -0800, Andrew Morton wrote: > On Fri, 13 Nov 2015 11:23:47 +0900 Joonsoo Kimwrote: > > > 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 >textdata bss dec hex filename >2972 112109641801054 mm/page_isolation.o-before >4608 570184070181b6a mm/page_isolation.o-after > > This seems an excessive amount of bloat for one little tracepoint. Is > this expected and normal (and acceptable)? Hello, I checked bloat on other tracepoints and found that it's normal. It takes 1KB more per tracepoint. Thanks. -- 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/
Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On Fri, 13 Nov 2015, Joonsoo Kim 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. > > Acked-by: Michal Nazarewicz > Signed-off-by: Joonsoo Kim Acked-by: David Rientjes Thanks for generalizing this! -- 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/
Re: [PATCH 2/3] mm/page_isolation: add new tracepoint, test_pages_isolated
On Fri, 13 Nov 2015, Joonsoo Kim 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. > > Acked-by: Michal Nazarewicz> Signed-off-by: Joonsoo Kim Acked-by: David Rientjes Thanks for generalizing this! -- 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/