Debugging writeback issues and tuning an application's writeback activity is easier when the activity is visible. With large clusters, classifying and root causing writeback problems has been a big headache. This patch series contains a series of patches that our team has been using to start getting a handle on writeback behaviour. These changes should be helpful for single system maintainers also. It's still a big headache. Once these changes are reviewed I will make sure the Documentation files are updated, but I expect some back and forth first. Michael Rubin (3): writeback: Creating /sys/kernel/mm/writeback/writeback writeback: per bdi monitoring writeback: tracking subsystems causing writeback drivers/base/node.c | 14 +++++ fs/buffer.c | 2 +- fs/fs-writeback.c | 28 +++++++-- fs/nilfs2/segment.c | 4 +- fs/sync.c | 2 +- include/linux/backing-dev.h | 9 +++ include/linux/mmzone.h | 2 + include/linux/writeback.h | 50 +++++++++++++++- mm/backing-dev.c | 137 ++++++++++++++++++++++--------------------- mm/mm_init.c | 122 ++++++++++++++++++++++++++++++++++++++ mm/page-writeback.c | 18 ++++-- mm/vmscan.c | 3 +- mm/vmstat.c | 2 + 13 files changed, 311 insertions(+), 82 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
