lkml.org 
[lkml]   [2009]   [May]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [tracing] ring_buffer question
    From
    Date
    On Sun, 2009-05-17 at 17:08 -0400, Jon Masters wrote:

    > Is there any reason you can think of why we don't just generalize
    > kernel/trace/ring_buffer into kernel/ring_buffer, remove the static
    > per_cpu buffer allocation and have this available for non-tracing?

    Ignore the latter point - I realize that I can use ring_buffer_alloc,
    etc. quite happily. I am doing that now in my smi_detector rewrite. But
    I still think the RB is a little too tracing specific - so, perhaps we
    can move it out of kernel/trace. I'll write up something once I've
    figured out this stuff to go along with the excellent trace docs since
    the generic ring buffer implementation is really quite sexy stuff.

    [thinking out loud] Does the global disable stuff also disable other
    non-tracing ring buffers?

    Jon.




    \
     
     \ /
      Last update: 2009-05-18 02:45    [W:0.025 / U:0.672 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site