lkml.org 
[lkml]   [2012]   [Jun]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: big allocation failure during tracing init.
On Wed, Jun 27, 2012 at 08:52:43PM -0400, Steven Rostedt wrote:
> On Fri, 2012-06-22 at 15:36 -0400, Dave Jones wrote:
>
> > I guess the problem is on kernels built with CONFIG_MAXCPUS, struct trace_iterator
> > can be pretty large due to this embedded in it..
> >
> > struct ring_buffer_iter *buffer_iter[NR_CPUS];
> >
> > Any thoughts on how to change that to a smaller dynamic data structure,
> > without adding too much overhead to tracing ? (I'm assuming a linked-list walk
> > for eg would be excessive?)
> >
>
> Does this patch fix it for you?

I'm not sure what I did to trigger the allocation failure last time,
but I'll run with this for a while, and see if anything falls out.

thanks!

Dave


\
 
 \ /
  Last update: 2012-06-28 05:01    [W:0.457 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site