From owner-freebsd-current Mon Feb 9 03:19:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11283 for current-outgoing; Mon, 9 Feb 1998 03:19:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11274; Mon, 9 Feb 1998 03:19:02 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id MAA21892; Mon, 9 Feb 1998 12:20:45 +0100 (CET) Date: Mon, 9 Feb 1998 12:20:44 +0100 (CET) From: Andrzej Bialecki To: Dmitrij Tejblum cc: dyson@FreeBSD.ORG, Mike Smith , tlambert@primenet.com, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-Reply-To: <199802081336.QAA15578@tejblum.dnttm.rssi.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Feb 1998, Dmitrij Tejblum wrote: > "John S. Dyson" wrote: > > I think that I might have misinformed here. Gzipped binaries need swap > > backing store for each page in the image even for .text section, when > > physical memory space needs to be freed for another page. Non-gzipped > > binaries can depend on paging off of the a.out itself. Also, non-gzipped > > binaries don't have to page out the .text for the initial freeing of the > > .text space. Gzipped binaries need to page out the .text pages when they > > are individually freed due to pageout daemon activity. Also, gzipped > > binaries are not demand-loaded, but are loaded at startup. > > Also, (unpacked) .text section of gzipped binaries is not shared among > several copies of same program, like in case of normal program. If I > understand correctly, this is a big problem for Andrzej, since all his > program is crunched together. Yes, it hurts :-). That's why I conducted several tests with making a dynamic crunch, to save at least on libraries. But in reality it proved to take more space in case of minimal system, than statically linked binary (if you count the size of objects taken from libc for statical linking, it may be relatively small depending on functions used by program; while when dynamically linked we have to load the whole libc [ca. 450kB] whether we use all the parts or not). It would be very interesting to know (if it's at all possible) how much space is occupied on running system by libraries only. Is it somehow related to "shared" pages? BTW. if someone can use this (I mean, dynamic version of crunched binaries), I can send a patch to crunchgen - it's trivial anyway. It would allow for generating both kinds of crunches, depending on a command line switch. Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message