From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function Date: Tue, 10 Nov 2009 22:34:56 -0800 Message-ID: <20091110223456.01ef355f@infradead.org> References: <20091025225342.007138f5@infradead.org> <20091111020108.GA11423@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Christoph Hellwig , Al Viro , mingo@elte.hu, Frederic Weisbecker , auke-jan.h.kok@intel.com To: Wu Fengguang Return-path: Received: from casper.infradead.org ([85.118.1.10]:56652 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752355AbZKKGd2 (ORCPT ); Wed, 11 Nov 2009 01:33:28 -0500 In-Reply-To: <20091111020108.GA11423@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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???? -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org