Dan Mick wrote:
> Roland Mainz wrote:
> > Dan Mick wrote:
> >> Roland Mainz wrote:
> >>> Peter Memishian wrote:
> >>>>  > > Actual data (from Kit Chow's recent tests): building with 
> >>>> -xstrconst saves
> >>>>  > > 389K of text on a DEBUG kernel.  Certainly not "~~10.1MB", but 
> >>>> non-trivial.
> >>>>  >
> >>>>  > Is that just "genunix" or the whole kernel with all modules ?
> >>>>
> >>>> Just genunix and unix, I believe.
> >>> How much is saved when the whole kernerl with all modules gets compiled
> >>> with "-xstrconst" ?
> >> There isn't any kernel compilation step that "compiles" kernel modules 
> >> against
> >> the kernel.  The closest we have is global lint and ctf manipulation.
> > [snip]
> >
> > Erm... lets rephrase my question: What's the amount of disk space saved
> > in $ROOT if we recompile the usr/src/uts/ subdir with "-xstrconst"
> > enabled for all code in this subdir (uhm... I can't test that myself...
> > my machine would need around two or three days to compile such a test
> > run... ;-( ) ?
> 
> All that would do is make the modules eliminate duplicate strings inside
> themselves,

Right...

> and I imagine that would not save very much.

... I am not sure. That's why I am asking for help to get real numbers.

> 2-3 days??  Good god, are you running Solaris thru three emulators on a 90MHz
> machine?  Building the entire tree, once, without lint, takes just over an 
> hour
> on any reasonably-cheap machine today...

This is an ancient Ultra5 which suffers from slow disks, memory shortage
and a user who is usually running his email client on the same machine,
too (read
http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2006-July/000643.html)
... ;-(

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) [EMAIL PROTECTED]
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to