On Mon, Jun 13, 2011 at 10:33:56PM +0800, Jan Kara wrote: > On Fri 10-06-11 22:48:05, Wu Fengguang wrote: > > [It seems beneficial to queue this simple trace event for > > next/upstream after the review?] > > > > Add trace event balance_dirty_state for showing the global dirty page > > counts and thresholds at each global_dirty_limits() invocation. This > > will cover the callers throttle_vm_writeout(), over_bground_thresh() > > and each balance_dirty_pages() loop. > OK, this might be useful. But shouldn't we also add similar trace point > for bdi limits? Otherwise the information is of limited use... Good point. The bdi limits will be exported in another balance_dirty_pages trace point. Thanks, Fengguang -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>