using 3390 mod9s 3190

I had done a lot of virtual memory (internal) enhancements on cp-67 and moved them over to vm-370 (again internal). some of those enhancements were eventually picked up and shipped in the product ... like a small subset of the stuff around what they called DCSS. It did also included a "paged mapped" filesystem infrastructure for CMS ... which would have greatly enhanced the sharing and caching of CMS information. misc. collected posts discussion page mapped stuff

the pagged map transition apparently was to great of a paradigm change (although I had done quite a bit of work on providing compatible semantics for existing operation) ... and never shipped. given the full page mapped semantics, sharing and caching of all cms stuff becomes trivially straight-forward.

using 3390 mod9s 3192
ref: part of the caching-electronic store discussions that on in the 70s had to do with...

CMS was otherwise a significantly file intensive infrastructure (especially by pc standards) which was only partially mitigated by things like placing small amounts of high-use CMS stuff in (DCSS) shared segments.

This became extremely painfully apparent with XT-370 ... in was single user operation in ibm-pc frame with all vm and cms stuff mapped to standard ibm-xt 110ms (access) disks. None of the sharing stuff held any benefit ... since you were the only one on the system (and the available storage was also painfully limited by mainframe standards).

some past discussion of xt-370

using 3390 mod9s 3191
Ron and Jenny Hawkins there were also the electronic memory "1655" that emulated 2305, several hundred were made available for internal installations. i was somewhat caught by the explanation for the vendor's 1655s. supposedly...

List | Previous | Next

using 3390 mod9s 3191

Alt Folklore Computers from Newsgroups

The #1 Usenet Provider on the Internet

using 3390 mod9s 3189

PLEX86 x86- Virtual Machine (VM) Program


	CVS \| Mailing List \| Download \| Newsgroups

		using 3390 mod9s 3190 I had done a lot of virtual memory (internal) enhancements on cp-67 and moved them over to vm-370 (again internal). some of those enhancements were eventually picked up and shipped in the product ... like a small subset of the stuff around what they called DCSS. It did also included a "paged mapped" filesystem infrastructure for CMS ... which would have greatly enhanced the sharing and caching of CMS information. misc. collected posts discussion page mapped stuff the pagged map transition apparently was to great of a paradigm change (although I had done quite a bit of work on providing compatible semantics for existing operation) ... and never shipped. given the full page mapped semantics, sharing and caching of all cms stuff becomes trivially straight-forward. using 3390 mod9s 3192 ref: part of the caching-electronic store discussions that on in the 70s had to do with... CMS was otherwise a significantly file intensive infrastructure (especially by pc standards) which was only partially mitigated by things like placing small amounts of high-use CMS stuff in (DCSS) shared segments. This became extremely painfully apparent with XT-370 ... in was single user operation in ibm-pc frame with all vm and cms stuff mapped to standard ibm-xt 110ms (access) disks. None of the sharing stuff held any benefit ... since you were the only one on the system (and the available storage was also painfully limited by mainframe standards). some past discussion of xt-370 using 3390 mod9s 3191 Ron and Jenny Hawkins there were also the electronic memory "1655" that emulated 2305, several hundred were made available for internal installations. i was somewhat caught by the explanation for the vendor's 1655s. supposedly... -- List \| Previous \| Next



		using 3390 mod9s 3191 Alt Folklore Computers from Newsgroups The #1 Usenet Provider on the Internet using 3390 mod9s 3189