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: Wed, 11 Nov 2009 08:19:05 -0800 Message-ID: <20091111081905.270a4e55@infradead.org> References: <20091025225342.007138f5@infradead.org> <20091111020108.GA11423@localhost> <20091110223456.01ef355f@infradead.org> <4AFA6AEF.5060306@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Wu Fengguang , 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: Jeff Garzik Return-path: In-Reply-To: <4AFA6AEF.5060306@garzik.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 11 Nov 2009 02:42:39 -0500 Jeff Garzik wrote: > On 11/11/2009 01:34 AM, Arjan van de Ven wrote: > > Wu Fengguang wrote: > >> 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???? > > Inode numbers have always been visible to userspace... IIRC, tar(1) > uses the st_ino member of struct stat to detect hard links in certain > cases. ls(1) displays inode numbers with -i, find(1) looks for them > with -inum, ... ok let me rephrase that. What would a user DO with this inode number information, given that the filename is already passed on; what additional useful, not-infinitely-hard-to-get piece of information does this give the user that he can use to do that he cannot do with the current information ? E.g. what is that ? -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org