summaryrefslogtreecommitdiffstats
path: root/fs/bad_inode.c
diff options
context:
space:
mode:
authorWu Fengguang <fengguang.wu@intel.com>2010-12-01 17:33:37 -0600
committerWu Fengguang <fengguang.wu@intel.com>2011-06-08 08:25:23 +0800
commit251d6a471c831e22880b3c146bb4556ddfb1dc82 (patch)
tree5ea61b9153866eda9f4164bf316c03786e1a7840 /fs/bad_inode.c
parent846d5a091b0506b75489577cde27f39b37a192a4 (diff)
downloadblackbird-op-linux-251d6a471c831e22880b3c146bb4556ddfb1dc82.tar.gz
blackbird-op-linux-251d6a471c831e22880b3c146bb4556ddfb1dc82.zip
writeback: trace event writeback_single_inode
It is valuable to know how the dirty inodes are iterated and their IO size. "writeback_single_inode: bdi 8:0: ino=134246746 state=I_DIRTY_SYNC|I_SYNC age=414 index=0 to_write=1024 wrote=0" - "state" reflects inode->i_state at the end of writeback_single_inode() - "index" reflects mapping->writeback_index after the ->writepages() call - "to_write" is the wbc->nr_to_write at entrance of writeback_single_inode() - "wrote" is the number of pages actually written v2: add trace event writeback_single_inode_requeue as proposed by Dave. CC: Dave Chinner <david@fromorbit.com> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Diffstat (limited to 'fs/bad_inode.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud