Date: Fri, 10 Nov 2000 17:33:56 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: dillon@earth.backplane.com (Matt Dillon) Cc: bright@wintelcom.net (Alfred Perlstein), arch@FreeBSD.ORG Subject: Re: The shared /bin and /sbin bikeshed Message-ID: <200011101733.KAA21973@usr08.primenet.com> In-Reply-To: <200011100326.eAA3Q6015450@earth.backplane.com> from "Matt Dillon" at Nov 09, 2000 07:26:06 PM
next in thread | previous in thread | raw e-mail | index | archive | help
> Linking with a shared library eats memory at run time. It's that simple. > Shared libraries make life easier but they do *NOT* generally reduce > the run time in-core memory footprint of a machine. Dynamic executables > actually increase the number of dirty pages the system has to cope with, > at least for discretely-run programs, and they tend to force the entire > shared library into core. > > Its a wash for programs that fork since the library relocations have > already been done by the time you get to the fork, thus all the forked > copies share the original parent's dirty library relocation pages. I've often wondered why no one has bothered to do the necessary work to share relocation pages between instances of the same program, which are not the results of a fork. Actually, I think there was a project at the UofU at one time that supported this, but all the code was in C++, and at the time, the C++ technology on virtual base class construction made it pretty much of a loss. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011101733.KAA21973>