Prev: [PATCH 3/4] writeback: pay attention to wbc->nr_to_write in write_cache_pages
Next: x86: Do not write to VGA memory space if CONFIG_VGA_CONSOLE is undefined
From: Dave Chinner on 19 Apr 2010 22:50
This series contains the initial writeback tracing patches from
Jens, as well as the extensions I added to provide visibility into
writeback control structures as the are used by the writeback code.
The visibility given is sufficient to understand what is happening
in the writeback path - what path is writing data, what path is
blocking on congestion, etc, and to determine the differences in
behaviour for different sync modes and calling contexts. This
tracing really needs to be integrated into mainline so that anyone
can improve the tracing as they use it to track down problems
in our convoluted writeback paths.

The remaining patches are fixes to problems that the new tracing
highlighted.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 3/4] writeback: pay attention to wbc->nr_to_write in write_cache_pages
Next: x86: Do not write to VGA memory space if CONFIG_VGA_CONSOLE is undefined