Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/6\]\s+writeback\:\s+initial\s+tracing\s+support\s*$/: 11 ]

Total 11 documents matching your query.

1. [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 25 May 2010 20:54:07 +1000
Trace queue/sched/exec parts of the writeback loop. Signed-off-by: Jens Axboe <jens.axboe@xxxxxxxxxx> Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> -- fs/fs-writeback.c | 40 +++++++-- include/tra
/archives/xfs/2010-05/msg00370.html (19,821 bytes)

2. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 25 May 2010 07:13:26 -0400
It might be worth to add a comment why this is in an unusal place. Otherwise looks good, Reviewed-by: Christoph Hellwig <hch@xxxxxx>
/archives/xfs/2010-05/msg00375.html (9,481 bytes)

3. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 27 May 2010 14:32:33 -0700
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
/archives/xfs/2010-05/msg00445.html (13,688 bytes)

4. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 28 May 2010 10:44:16 +1000
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
/archives/xfs/2010-05/msg00455.html (13,569 bytes)

5. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Steven Rostedt <rostedt@xxxxxxxxxxx>
Date: Thu, 27 May 2010 21:18:21 -0400
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
/archives/xfs/2010-05/msg00457.html (12,660 bytes)

6. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Steven Rostedt <rostedt@xxxxxxxxxxx>
Date: Thu, 27 May 2010 21:20:57 -0400
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,
/archives/xfs/2010-05/msg00458.html (12,653 bytes)

7. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 28 May 2010 03:45:00 -0400
These two lines are just moved down a bit by the patch, I think any cleanups should be left to separate patches.
/archives/xfs/2010-05/msg00463.html (11,895 bytes)

8. [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 4 Jun 2010 09:55:23 +1000
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
/archives/xfs/2010-06/msg00039.html (20,854 bytes)

9. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Li Zefan <lizf@xxxxxxxxxxxxxx>
Date: Fri, 04 Jun 2010 09:10:33 +0800
Should use strlcpy() ? ditto ... ditto
/archives/xfs/2010-06/msg00043.html (12,138 bytes)

10. Re: [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 4 Jun 2010 11:24:16 +1000
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
/archives/xfs/2010-06/msg00044.html (22,327 bytes)

11. [PATCH 1/6] writeback: initial tracing support (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 8 Jun 2010 10:38:02 +1000
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
/archives/xfs/2010-06/msg00069.html (20,237 bytes)


This search system is powered by Namazu