Re: [PATCH] tracing/ring_buffer: Try harder to allocate

2017-07-11 Thread Johannes Weiner
On Mon, Jul 10, 2017 at 11:05:00PM -0700, 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 > implementatio

Re: [PATCH] tracing/ring_buffer: Try harder to allocate

2017-07-10 Thread Vlastimil Babka
On 07/11/2017 08:05 AM, 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-r

Re: [PATCH] tracing/ring_buffer: Try harder to allocate

2017-07-10 Thread Michal Hocko
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

[PATCH] tracing/ring_buffer: Try harder to allocate

2017-07-10 Thread Joel Fernandes
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 fin