Messages in this thread | | | Date | Wed, 11 Nov 2009 14:40:27 +0800 | From | Wu Fengguang <> | Subject | Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function |
| |
On Wed, Nov 11, 2009 at 02:34:56PM +0800, Arjan van de Ven wrote: > On Wed, 11 Nov 2009 10:01:08 +0800 > Wu Fengguang <fengguang.wu@intel.com> wrote: > > > 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? > > what can a user do with an inode number????
Hmm, maybe to tell one file from another in the trace stream :) And maybe to compare it with other data sources, like "ls -i".
Thanks, Fengguang
| |