Re: [RFC PATCH 16/22 -v2] add get_monotonic_cycles

Frank Ch. Eigler
2008-01-17T20:42:58Z

Hi -

On Thu, Jan 17, 2008 at 03:08:33PM -0500, Steven Rostedt wrote:
> [...]
> + trace_mark(kernel_sched_schedule,
> + "prev_pid %d next_pid %d prev_state %ld",
> + prev->pid, next->pid, prev->state);
> [...]
> But...
>
> Tracers that want to do a bit more work, like recording timings and seeing
> if we hit some max somewhere, can't do much with that pretty print data.

If you find yourself wanting to perform computations like finding
maxima, or responding right there as opposed to later during userspace
trace data extraction, then you're trending toward a tool like
systemtap.

> [...]
> So, at a minimum, I'd like to at least have meta data attached:
> trace_mark(kernel_sched_schedule,
> "prev_pid %d next_pid %d prev_state %ld\0"
> "prev %p next %p",
> prev->pid, next->pid, prev->state,
> prev, next);
>
> This would allow for both the nice pretty print of your trace, as well as
> allowing other tracers to get to better meta data.

Yes, more self-contained marker events are necessary for meaningful
in-situ processing. That needs to be balanced by the increased cost
for computing and passing the extra parameters, multiplied the event
occurrence rate.

In this case, the prev/next pointers are sufficient to compute the
other values. For particularly performance-critical markers, it may
not be unreasonable to expect the callback functions to dereference
such pointers for pretty-printing or other processing.

> The '\0' would keep your tracer from recording the extra data, and we
> could add some way to ignore the parameters in the printf to let other
> traces get straight to the meta data.

This \0 hack is perhaps too clever. Much of the cost of the extra
parameters is already paid by the time that a simpleminded tracing
callback function starts going through the string. Also, I believe
the systemtap marker interface would break if the format strings were
not singly terminated ordinary strings.

- FChE