Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755316AbdGKGMx (ORCPT ); Tue, 11 Jul 2017 02:12:53 -0400 Received: from mx2.suse.de ([195.135.220.15]:56057 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755251AbdGKGMw (ORCPT ); Tue, 11 Jul 2017 02:12:52 -0400 Date: Tue, 11 Jul 2017 08:12:45 +0200 From: Michal Hocko To: Joel Fernandes Cc: linux-kernel@vger.kernel.org, kernel-team@android.com, linux-mm@kvack.org, Alexander Duyck , Mel Gorman , Hao Lee , Vladimir Davydov , Johannes Weiner , Joonsoo Kim , Tim Murray , Ingo Molnar , Steven Rostedt , stable@vger.kernel.org Subject: Re: [PATCH] tracing/ring_buffer: Try harder to allocate Message-ID: <20170711061245.GC24852@dhcp22.suse.cz> References: <20170711060500.17016-1-joelaf@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170711060500.17016-1-joelaf@google.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3093 Lines: 80 On Mon 10-07-17 23:05:00, Joel Fernandes wrote: > ftrace can fail to allocate per-CPU ring buffer on systems with a large > number of CPUs coupled while large amounts of cache happening in the > page cache. Currently the ring buffer allocation doesn't retry in the VM > implementation even if direct-reclaim made some progress but still > wasn't able to find a free page. On retrying I see that the allocations > almost always succeed. The retry doesn't happen because __GFP_NORETRY is > used in the tracer to prevent the case where we might OOM, however if we > drop __GFP_NORETRY, we risk destabilizing the system if OOM killer is > triggered. To prevent this situation, use the __GFP_RETRY_MAYFAIL flag > introduced recently [1]. > > Tested the following still succeeds without destabilizing a system with > 1GB memory. > echo 300000 > /sys/kernel/debug/tracing/buffer_size_kb > > [1] https://marc.info/?l=linux-mm&m=149820805124906&w=2 Yes this is the correct usage of the new flag. > Cc: Alexander Duyck > Cc: Mel Gorman > Cc: Hao Lee > Cc: Vladimir Davydov > Cc: Johannes Weiner > Cc: Joonsoo Kim > Cc: Michal Hocko > Cc: Tim Murray > Cc: Ingo Molnar > Cc: Steven Rostedt > Cc: stable@vger.kernel.org I do not think stable tag is appropriate. The new flag hasn't been merged yet and it is not a stable material. > Signed-off-by: Joel Fernandes Feel free to add Acked-by: Michal Hocko > --- > kernel/trace/ring_buffer.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c > index 4ae268e687fe..529cc50d7243 100644 > --- a/kernel/trace/ring_buffer.c > +++ b/kernel/trace/ring_buffer.c > @@ -1136,12 +1136,12 @@ static int __rb_allocate_pages(long nr_pages, struct list_head *pages, int cpu) > for (i = 0; i < nr_pages; i++) { > struct page *page; > /* > - * __GFP_NORETRY flag makes sure that the allocation fails > - * gracefully without invoking oom-killer and the system is > - * not destabilized. > + * __GFP_RETRY_MAYFAIL flag makes sure that the allocation fails > + * gracefully without invoking oom-killer and the system is not > + * destabilized. > */ > bpage = kzalloc_node(ALIGN(sizeof(*bpage), cache_line_size()), > - GFP_KERNEL | __GFP_NORETRY, > + GFP_KERNEL | __GFP_RETRY_MAYFAIL, > cpu_to_node(cpu)); > if (!bpage) > goto free_pages; > @@ -1149,7 +1149,7 @@ static int __rb_allocate_pages(long nr_pages, struct list_head *pages, int cpu) > list_add(&bpage->list, pages); > > page = alloc_pages_node(cpu_to_node(cpu), > - GFP_KERNEL | __GFP_NORETRY, 0); > + GFP_KERNEL | __GFP_RETRY_MAYFAIL, 0); > if (!page) > goto free_pages; > bpage->page = page_address(page); > -- > 2.13.2.725.g09c95d1e9-goog -- Michal Hocko SUSE Labs