From owner-freebsd-current Wed Sep 2 05:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06797 for freebsd-current-outgoing; Wed, 2 Sep 1998 05:10:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06792 for ; Wed, 2 Sep 1998 05:10:39 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id IAA07647; Wed, 2 Sep 1998 08:20:01 -0400 (EDT) Date: Wed, 2 Sep 1998 08:20:01 -0400 (EDT) From: Charles Youse To: Bruce Evans cc: tlambert@primenet.com, current@FreeBSD.ORG, jdp@polstra.com, reilly@zeta.org.au Subject: Re: ELF binaries size In-Reply-To: <199809020743.RAA14655@godzilla.zeta.org.au> 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 Wed, 2 Sep 1998, Bruce Evans wrote: > >> 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). > > > >Actually, it implies that the x86 architecture wastes a full page of > >memory, by not supportin byte-level protection resoloution. > > Except using byte-granularity segments. How is this handled on non-segmented architectures? I realize that FreeBSD's target has always been i386, but this would indeed be a complicated matter on say, a Sparc. Chuck Youse cyouse@syncom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message