On Thursday 28 August 2008 14:06, Andrew Morton wrote: > On Thu, 28 Aug 2008 09:18:16 +0530 "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx> wrote: > > > This is now too large to be inlined. > > > > How do we actually figure that out ? I have been making that mistakes > > quiet often. > > Well. Experience and guesswork, mainly. > > But a useful metric is to look and the /bin/size output before and > after the inlining. In this case fs/ext3/ialloc.o's text shrunk 40-odd > bytes, which we think is a net benefit due to reduced CPU cache > pressure. Weighed against register save/restore, compiler barrier, and function call cost of uninlined. These can add up to 10s of cycles per call I've seen, so if it is called several times between each icache miss it can easily be worth inlining. Basically, measurement is required, and if it isn't important enough to measure policy tends to default to uninline if that saves space. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
