From: fche@redhat.com (Frank Ch. Eigler) Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function Date: Wed, 11 Nov 2009 18:10:15 -0500 Message-ID: References: <20091025225342.007138f5@infradead.org> <20091111020108.GA11423@localhost> <20091110223456.01ef355f@infradead.org> <4AFA6AEF.5060306@garzik.org> <20091111081905.270a4e55@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeff Garzik , 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: Arjan van de Ven Return-path: In-Reply-To: <20091111081905.270a4e55@infradead.org> (Arjan van de Ven's message of "Wed, 11 Nov 2009 08:19:05 -0800") Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Arjan van de Ven writes: > [...] 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 [...] Perhaps "infinitely hard" is the wrong criterion, but passing inode numbers lets a tracepoint client track changes to the same file, even though the file may be renamed/unlinked over time. - FChE