Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+3\/6\]\s+writeback\:\s+Add\s+tracing\s+to\s+write_cache

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+3\/6\]\s+writeback\:\s+Add\s+tracing\s+to\s+write_cache_pages\s*$/: 3 ]

Total 3 documents matching your query.

1. [PATCH 3/6] writeback: Add tracing to write_cache_pages (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Fri, 4 Jun 2010 09:55:25 +1000; Add a trace event to the ->writepage loop in write_cache_pages to give visibility into how the ->writepage call is changing variables within the writeback control structure. Of most interest is how w; /archives/xfs/2010-06/msg00037.html (9,922 bytes)
2. Re: [PATCH 3/6] writeback: Add tracing to write_cache_pages (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Fri, 4 Jun 2010 03:51:27 -0400; Looks good, it might be worth to add another tracepoint for ->writepage from reclaim context so that we can start investigating the cases where that happens far too often. Reviewed-by: Christoph Hell; /archives/xfs/2010-06/msg00049.html (10,322 bytes)
3. [PATCH 3/6] writeback: Add tracing to write_cache_pages (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 8 Jun 2010 10:38:04 +1000; Add a trace event to the ->writepage loop in write_cache_pages to give visibility into how the ->writepage call is changing variables within the writeback control structure. Of most interest is how w; /archives/xfs/2010-06/msg00063.html (9,823 bytes)

Current List: 1 - 3
Page: [1]