Messages in this thread | | | From | Denis Vlasenko <> | Subject | Re: code bloat [was Re: Semaphore assembly-code bug] | Date | Mon, 1 Nov 2004 15:40:25 +0200 |
| |
On Monday 01 November 2004 13:27, Alan Cox wrote: > 2. Most of the pages of libxml2.so don't get paged in by a typical > application
This assumes that 'needed' functions are close together. This can be easily not the case, so you end up using only a fraction of fetched page's content.
Also this argument tend to defend library growth. "It's mostly unused, don't worry". What if that is not true? How to compare RAM footprint of new versus old lib in this case? Just believe that it didn't get worse?
This can't be checked easily: even -static compile can fail to help. glibc produce nearly 400kb executable for
int main() { return 0; }
because init code uses printf on error paths and that pulls i18n in. How many kilobytes is really runs - who knows... -- vda
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |