From owner-freebsd-current  Tue Sep  1 22:07:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA09616
          for freebsd-current-outgoing; Tue, 1 Sep 1998 22:07:45 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09605
          for <current@FreeBSD.ORG>; Tue, 1 Sep 1998 22:07:42 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA02087;
	Wed, 2 Sep 1998 15:06:39 +1000
Date: Wed, 2 Sep 1998 15:06:39 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199809020506.PAA02087@godzilla.zeta.org.au>
To: jdp@polstra.com, joelh@gnu.org
Subject: Re: ELF binaries size
Cc: bde@zeta.org.au, current@FreeBSD.ORG, reilly@zeta.org.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>> I think it implies that elf wastes a full page of memory (the space
>>> between the ':'s above) most of the time (unless the ':'s are on a
>>> page boundary), while aout only wastes an average of half a page
>>> (the space between the text ':' and the end of the page).
>> But a.out has a repeat of the same situation at the juncture of data
>> and bss, and ELF does not.

>Not to mention that this wastage only happens after a bit of data in
>the first data page is written to.  Before that, it's being shared
>with text, anyway.

This page is almost certain to be written to.  In all (2) cases that
I looked at, the data section begins with `__progname', which is always
written to very early by __main().  This page should be mapped writable
to begin with.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message