Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function

From: Wu Fengguang
Date: Tue Nov 10 2009 - 21:01:21 EST

Hi Arjan,

> + TP_printk("task=%i (%s) file=%s dev=%s",
> + __entry->pid, __entry->comm, __entry->file, __entry->dev)

Maybe this is enough for POWERTOP, however for general use, the dirty
type(data/metadata) and inode number may be valuable to some users?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at