Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!elroy.jpl.nasa.gov!jpl-devvax!lwall
From: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: undump on a Sun OS 4.x
Message-ID: <8868@jpl-devvax.JPL.NASA.GOV>
Date: 25 Jul 90 18:23:14 GMT
References: <1990Jul25.163414.14380@midway.uchicago.edu>
Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)
Distribution: na
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 17

In article <1990Jul25.163414.14380@midway.uchicago.edu> brian@oddjob.UChicago.EDU () writes:
: 
: Does anyone have an undump which will work in conjunction
: with perl's 'dump' under SunOS 4.x?
: 
: I have a large set of perl subroutines (2MB worth of runtime memory) 
: which fork copies of themselves
: several times. I am interested in getting the operating system to
: 'share' the perl subroutines (treat them as 'code' rather than 'data')
: and not make a separate data space for each forked copy. Is this
: possible with 'dump'?

With SunOS 4.x, if you read in the data pages before forking, they should
be shared, since (I believe) they're set up as copy-on-write.  However,
undumping should help your startup time.

Larry