From owner-freebsd-hackers Tue Feb 27 11:36:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id 9900D37B718 for ; Tue, 27 Feb 2001 11:36:41 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.2/8.11.2) with ESMTP id f1RJaFq98998; Tue, 27 Feb 2001 12:36:15 -0700 (MST) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200102271936.f1RJaFq98998@orthanc.ab.ca> From: Lyndon Nerenberg Organization: The Frobozz Magic Homing Pigeon Company To: Tony Finch Cc: Peter Seebach , freebsd-hackers@FreeBSD.ORG Subject: Re: [hackers] Re: Setting memory allocators for library functions. In-reply-to: Your message of "Tue, 27 Feb 2001 01:37:43 GMT." <20010227013743.H609@hand.dotat.at> Date: Tue, 27 Feb 2001 12:36:15 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Tony" == Tony Finch writes: >> Well, to some extent, I have to wonder why all these pages are >> being requested if they aren't being used... Tony> fork() with big data segments that cause swap to be reserved Tony> in case of a copy-on-write. The 2GB of swap is never Tony> actually used, but you still have to have it. If the information in the data segment is going to be updated then you have to have writable backing store. If, however, that data is never going to be changed, it should be declared in the program as read-only data. The kernel VM system should not be working around applications that don't declare their data arena correctly. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message