From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH 18/20] ceph: debugging Date: Fri, 17 Jul 2009 22:01:14 +0200 Message-ID: <20090717200114.GA6173@basil.fritz.box> References: <1247693090-27796-15-git-send-email-sage@newdream.net> <1247693090-27796-16-git-send-email-sage@newdream.net> <1247693090-27796-17-git-send-email-sage@newdream.net> <1247693090-27796-18-git-send-email-sage@newdream.net> <1247693090-27796-19-git-send-email-sage@newdream.net> <87d480x16p.fsf@basil.nowhere.org> <20090717185641.GH8046@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andi Kleen , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Sage Weil Return-path: Received: from one.firstfloor.org ([213.235.205.2]:34717 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752053AbZGQUBS (ORCPT ); Fri, 17 Jul 2009 16:01:18 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Jul 17, 2009 at 12:52:33PM -0700, Sage Weil wrote: > > > ceph_file_part(__FILE__, sizeof(__FILE__)), \ > > > __LINE__, args); > > > > That seems like a wasteful way to do this -- i bet you could > > shrink binary size with debugging on considerably if you move > > the file_part into a function. > > If you mean ceph_file_part shouldn't be inline, definitely. Beyond that > I'm not sure what more to change... it's just a few extra chars on the > format string and 2 calls instead of 1? Yes, but you have hundreds/thousands of these calls don't you? If you have two calls here instead of one and that costs let's say 20 bytes of code and 1000 calls it's already 20K of binary size. Perhaps code size is not your highest priority now, but obvious inefficiencies like this are not good. -Andi -- ak@linux.intel.com -- Speaking for myself only.