Date: Tue, 1 Sep 1998 23:23:01 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: tlambert@primenet.com Cc: reilly@zeta.org.au, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: ELF binaries size Message-ID: <199809020423.XAA03734@detlev.UUCP> In-Reply-To: <199809020137.SAA13431@usr01.primenet.com> (message from Terry Lambert on Wed, 2 Sep 1998 01:37:48 %2B0000 (GMT)) References: <199809020137.SAA13431@usr01.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From reading the sources, I think this does not happen (it would be > hard to make the vnode pager function in the presence of a unified VM > and buffer cache, if this were going on ;-)), and the sections are > loaded starting(/ending) on page boundaries, only for their length. Why would that be difficult, with COW? > What this means is that it takes the same space in core, but less > space on disk, and that the padding is implied, and an odd boundary > is seen as a negative offset (i.e., the first part of the first > data page is mapped, but not valid). Given where the pages come > from, this should not expose "old data" in the gaps. Just out of curiousity... IIRC, the bss will be started dw-aligned, yes? Does that mean that there would be, in theory, some old data in the gap between data and bss? (iff (edata%4)!=0, of course.) Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809020423.XAA03734>