From: Ted Ts'o Subject: Re: [PATCH 23/23] ext4: add some tracepoints in ext4/extents.c Date: Fri, 8 Jul 2011 19:20:10 -0400 Message-ID: <20110708232010.GK3331@thunk.org> References: <1309970166-11770-1-git-send-email-tytso@mit.edu> <1309970166-11770-24-git-send-email-tytso@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ext4 Developers List , Aditya Kali To: Eric Gouriou Return-path: Received: from li9-11.members.linode.com ([67.18.176.11]:49820 "EHLO test.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750931Ab1GHXUM (ORCPT ); Fri, 8 Jul 2011 19:20:12 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On Wed, Jul 06, 2011 at 11:12:30AM -0700, Eric Gouriou wrote: > > In all the trace points that capture the logical block/physical > block/length of an extent, it would be nicer to pass the extent itself > as a parameter and perform the extraction in the TP_fast_assign() > block. This requires adding an #include above the > include of in fs/ext4/super.c in order to > have ext4_ext_pblock() and ext4_ext_get_actual_len() available. > > By itself this should not be ground to respin the whole patch series, > a follow-on cleanup patch would do (I volunteer to create one if > desired). Fortunately this wouldn't cause the trace record format to > change, so it wouldn't cause any backward/forward compatibility issue. Good suggestion, I've made this change. - Ted