-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi John, many thanks for that excellent URL, it's an exact an answer to my question :-)
The explanation does however lean on z/VM's algorithms as being the potential need for Expanded storage, and the 2GB problem went away with z/VM 5.2. An OS that need to cache "active" working sets, only needs to do so when it runs out of sufficient Central storage. By moving Central storage to Expanded storage one only exacerbates the problem. Mark John Schnitzler Jr wrote: > Here is a pretty good webpage that describes the reasons for VM's need for > expanded storage. > > http://www.vm.ibm.com/perf/tips/storconf.html > > John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFS5CB+CA7PBRBnXQRAnYxAJ9A6iLCliS2hwqBi3d9vEvRDou9rQCgtzww MhF8OrI/+oT1uX+7amOaoiY= =f0LB -----END PGP SIGNATURE----- ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
