From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wu Fengguang Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function Date: Wed, 11 Nov 2009 14:40:27 +0800 Message-ID: <20091111064027.GA11565@localhost> References: <20091025225342.007138f5@infradead.org> <20091111020108.GA11423@localhost> <20091110223456.01ef355f@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , Christoph Hellwig , Al Viro , "mingo@elte.hu" , Frederic Weisbecker , "Kok, Auke-jan H" To: Arjan van de Ven Return-path: Content-Disposition: inline In-Reply-To: <20091110223456.01ef355f@infradead.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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 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