Introduce the BDI_DIRTIED counter. It will be used for estimating the bdi's dirty bandwidth. CC: Jan Kara <jack@xxxxxxx> CC: Michael Rubin <mrubin@xxxxxxxxxx> CC: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> Signed-off-by: Wu Fengguang <fengguang.wu@xxxxxxxxx> --- include/linux/backing-dev.h | 1 + mm/backing-dev.c | 2 ++ mm/page-writeback.c | 1 + 3 files changed, 4 insertions(+) --- linux-next.orig/include/linux/backing-dev.h 2011-04-14 09:21:06.000000000 +0800 +++ linux-next/include/linux/backing-dev.h 2011-04-14 21:51:23.000000000 +0800 @@ -40,6 +40,7 @@ typedef int (congested_fn)(void *, int); enum bdi_stat_item { BDI_RECLAIMABLE, BDI_WRITEBACK, + BDI_DIRTIED, BDI_WRITTEN, NR_BDI_STAT_ITEMS }; --- linux-next.orig/mm/page-writeback.c 2011-04-14 09:21:06.000000000 +0800 +++ linux-next/mm/page-writeback.c 2011-04-14 21:51:23.000000000 +0800 @@ -1133,6 +1133,7 @@ void account_page_dirtied(struct page *p __inc_zone_page_state(page, NR_FILE_DIRTY); __inc_zone_page_state(page, NR_DIRTIED); __inc_bdi_stat(mapping->backing_dev_info, BDI_RECLAIMABLE); + __inc_bdi_stat(mapping->backing_dev_info, BDI_DIRTIED); task_dirty_inc(current); task_io_account_write(PAGE_CACHE_SIZE); } --- linux-next.orig/mm/backing-dev.c 2011-04-14 09:21:06.000000000 +0800 +++ linux-next/mm/backing-dev.c 2011-04-14 21:51:23.000000000 +0800 @@ -86,6 +86,7 @@ static int bdi_debug_stats_show(struct s "BdiDirtyThresh: %8lu kB\n" "DirtyThresh: %8lu kB\n" "BackgroundThresh: %8lu kB\n" + "BdiDirtied: %8lu kB\n" "BdiWritten: %8lu kB\n" "b_dirty: %8lu\n" "b_io: %8lu\n" @@ -95,6 +96,7 @@ static int bdi_debug_stats_show(struct s (unsigned long) K(bdi_stat(bdi, BDI_WRITEBACK)), (unsigned long) K(bdi_stat(bdi, BDI_RECLAIMABLE)), K(bdi_thresh), K(dirty_thresh), K(background_thresh), + (unsigned long) K(bdi_stat(bdi, BDI_DIRTIED)), (unsigned long) K(bdi_stat(bdi, BDI_WRITTEN)), nr_dirty, nr_io, nr_more_io, !list_empty(&bdi->bdi_list), bdi->state); -- 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