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: Fri, 20 Nov 2009 08:45:37 -0800 Message-ID: <20091120084537.6e28ddd2@infradead.org> References: <20091025225342.007138f5@infradead.org> <20091111020108.GA11423@localhost> <20091110223456.01ef355f@infradead.org> <4AFA6AEF.5060306@garzik.org> <20091111081905.270a4e55@infradead.org> <4AFB4AC7.1090405@intel.com> <20091112072217.GA31719@elte.hu> <20091120104335.GB29143@infradead.org> <20091120064511.268cc8fd@infradead.org> <20091120160526.GD20634@shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , Ingo Molnar , "Kok, Auke" , "Frank Ch. Eigler" , Jeff Garzik , "Wu, Fengguang" , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , Al Viro , Frederic Weisbecker To: Jamie Lokier Return-path: In-Reply-To: <20091120160526.GD20634@shareable.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 20 Nov 2009 16:05:26 +0000 Jamie Lokier wrote: > Arjan van de Ven wrote: > > in my case it's not about finding the file, but finding the place in > > the application that is doing the writing. The last pathname > > component is more than enough for this.... > > So what you really need is the source file and line number in your > application where it does the writing :-) while you present this as a joke.... perf can more or less do this using the backtrace infrastructure ... -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org