>Anyway, pmap.o was just one of the biggest single files (it's about 14
>KB now), but the surprising effect of looking at the size figures is
>that the size is really summed up of numerous not-so-large files,
>where you wouldn't even get the idea that it will get up to 400 KB
>when looking at their sizes.
I get the same feeling looking at kernel profiles. There are usually
_lots_ of modules each taking up 0.5%-2% and nothing that can be
optimized easily. This is partly because all the high spots have
already been optimized and partly because there are a lot of layers.