On Fri, 2011-04-08 at 03:37 -0400, Steven Rostedt wrote: > I don't think this is about perf and ftrace as competitors, but they are > currently two different infrastructures that are existing in the kernel. > They are currently optimized for different purposes. ftrace is optimized > for system tracing (persistent buffers and such) where as perf is > optimized for user tracing. That's complete nonsense, perf isn't build for tracing at all, its just that tracing is a special case of the larger problem set of sampling/profiling it is build for. Nor is perf in any way shape or form better suited for user than for kernel space, it really doesn't care, if we'd only be interested in user crap we'd never have done NMI sampling for instance. > But the two can do both but the other > feature is not as efficient as the other tool. Well, neither can do user-space-tracing at all, simply because we don't have hooks into userspace, although the uprobes stuff looks to cure some of that. > As you said perf has a lot of overhead due to data that it saves per > event. Someday you should actually read the perf code before you say something. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
