On Fri, Jun 18, 2010 at 05:30:12PM -0700, Michael Rubin wrote: > 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 I'm not sure we want to export statistics that represent internal implementation details into a fixed userspace API. Who, other than developers, are going to understand and be able to make use of this information? FWIW, I've got to resend the writeback tracing patches to Jens that I have that give better visibility into the writeback behaviour. Perhaps those tracing events are a better basis for tracking down writeback problems - the bugs I found with the tracing could not have been found with these statistics... That's really why I'm asking - if the stats are just there to help development and debugging, then I think that improving the writeback tracing is a better approach to improving visibility of writeback behaviour... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>