It would be most useful if this patchset's description provided sample tracing output, so we can see what the patch is actually providing us. Could/should be implemented in C. So this is always zero
This is just a forward port of Jen's patch. I guess I'll have to clean it up some more... OK. I guess so. I'd forgotten that this was in the original patch.... OK. Every other trace event header does
That's intended. It is documented in samples/trace_events/trace-events-samples.h The purpose of the TRACE_HEADER_MULTI_READ is to read the trace header multi times. ;-) You can also read about it her
It's all part of the CPP voodoo ritual. You don't want to know why, just do it, otherwise you may find dancing CPP skulls running around your bathtub. If you want to be a CPP Voodoo Witch doctor too,
Trace queue/sched/exec parts of the writeback loop. This provides insight into when and why flusher threads are scheduled to run. e.g a sync invocation leaves a trace like: sync-2798 [006] 611323.335
Don't care. Updated patch below. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx writeback: initial tracing support Trace queue/sched/exec parts of the writeback loop. This provides insight into wh
Trace queue/sched/exec parts of the writeback loop. This provides insight into when and why flusher threads are scheduled to run. e.g a sync invocation leaves a trace like: sync-2798 [006] 611323.335