Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932095AbZKKXKh (ORCPT ); Wed, 11 Nov 2009 18:10:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759296AbZKKXKh (ORCPT ); Wed, 11 Nov 2009 18:10:37 -0500 Received: from mx1.redhat.com ([209.132.183.28]:14802 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759611AbZKKXKf (ORCPT ); Wed, 11 Nov 2009 18:10:35 -0500 To: Arjan van de Ven 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 Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function References: <20091025225342.007138f5@infradead.org> <20091111020108.GA11423@localhost> <20091110223456.01ef355f@infradead.org> <4AFA6AEF.5060306@garzik.org> <20091111081905.270a4e55@infradead.org> From: fche@redhat.com (Frank Ch. Eigler) Date: Wed, 11 Nov 2009 18:10:15 -0500 In-Reply-To: <20091111081905.270a4e55@infradead.org> (Arjan van de Ven's message of "Wed, 11 Nov 2009 08:19:05 -0800") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 712 Lines: 17 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/