Re: IBM 360 memory

Article View: comp.arch

Article #22941

#22941

From: Anne & Lynn Wheeler
Date: Sat, 20 Mar 2004 20:10

34 lines
3752 bytes

Anne & Lynn Wheeler <lynn@garlic.com> writes:
> tss/360 had concept of virtual memory and one-level store ... but
> almost not concept of performance techniques and dynanic adaptive
> anything. besides tss/360 horribly long pathlengths there were some
> static things that they just didn't stop and think about. CMS used a

slightly more digression; standard cms didn't have a virtual
memory file system ... it had a somewhat CTSS looking filesystem
using effectively real i/o semantics that got simulated in
cp/67's virtual memory environment .... recent slight
digression regarding CCWTRANS & UNTRANS simulating real I/O
CCW programs in virtual memory environment:
http://www.garlic.com/~lynn/2003c.html#59 real multi-tasking, multi-programming

in the early '70s, i did do a page-mapped infrastructure for the CMS
filesystem ... which supported general semantics ... being able to
somewhat do the one-level store stuff ... ala tss/360 ... but also
supporting the existing CMS filesystem semantics ... aka real I/O
operations were translated into block page read/write. From that
standpoint it supported the high-level block read/write semantics
standard in the cms filesystem ... but the underlying implementation
was signficantly more efficiently since it avoided the whole thing of
virtual to real translation, with page fixing/unfixing that had to go
on during the period of the simualted real i/o.

random past postings about paged/memory mapped filesystem:
http://www.garlic.com/~lynn/subtopic.html#mmap

in had the efficiency of using paging implementation with the tight &
efficient block read/write leveraging the higher level CMS filesystem
conventions.

-- 
Anne & Lynn Wheeler | http://www.garlic.com/~lynn/

Technical Details

Message-ID: <ur7vngu07.fsf@smtp.comcast.net>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!wn12feed!worldnet.att.net!216.196.106.140!border1.nntp.sjc.giganews.com!nntp.giganews.com!local1.nntp.sjc.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail

References:

<2de13727.0403170551.830d050@posting.google.com> <uish31o5f.fsf@mail.comcast.net> <405875B5.9080200@prodigy.net> <405B4E58.43B57F32@earthlink.net> <3DR6c.56693$H44.1048115@bgtnsc04-news.ops.worldnet.att.net> <u4qsjimyc.fsf@smtp.comcast.net> <slrnc5oodj.nj9.jmaynard@thebrain.conmicro.cx> <89po5014gki8tgmdaqfkkqsr82nlt6582n@4ax.com> <slrnc5oq0h.nlr.jmaynard@thebrain.conmicro.cx> <uvfkzh40g.fsf@smtp.comcast.net>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd705,6e80f3f01eb41450
X-Google-Attributes: gidfd705,public
X-Google-Thread: 103c88,16e4a17bee898890
X-Google-Attributes: gid103c88,public
X-Google-Thread: 102b75,695a3f924dc00251
X-Google-Attributes: gid102b75,public
X-Google-ArrivalTime: 2004-03-20 12:10:59 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!wn12feed!worldnet.att.net!216.196.106.140!border1.nntp.sjc.giganews.com!nntp.giganews.com!local1.nntp.sjc.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 20 Mar 2004 14:10:13 -0600
Newsgroups: comp.arch,alt.folklore.computers,bit.listserv.vmesa-l
Subject: Re: IBM 360 memory
Reply-To: Anne & Lynn Wheeler <lynn@garlic.com>
References: <2de13727.0403170551.830d050@posting.google.com> <uish31o5f.fsf@mail.comcast.net>
 <405875B5.9080200@prodigy.net> <405B4E58.43B57F32@earthlink.net>
 <3DR6c.56693$H44.1048115@bgtnsc04-news.ops.worldnet.att.net>
 <u4qsjimyc.fsf@smtp.comcast.net>
 <slrnc5oodj.nj9.jmaynard@thebrain.conmicro.cx>
 <89po5014gki8tgmdaqfkkqsr82nlt6582n@4ax.com>
 <slrnc5oq0h.nlr.jmaynard@thebrain.conmicro.cx>
 <uvfkzh40g.fsf@smtp.comcast.net>
From: Anne & Lynn Wheeler <lynn@garlic.com>
Date: Sat, 20 Mar 2004 13:10:00 -0700
Message-ID: <ur7vngu07.fsf@smtp.comcast.net>
Organization: Wheeler&Wheeler
User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (windows-nt)
Cancel-Lock: sha1:MGqUdysBaABaKEcHTVWqM7GLTB4=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 34
NNTP-Posting-Host: 24.9.111.164
X-Trace: sv3-QAa65nQsPhxuQOfWaHM2BZFtKVMTraz4V0qId7RN9DHOpdxZ7EHcx6RzXBKMj7gVaDxQIx5aQ5G3hmd!zjZzuKUv+tFn9LfddjNgq0y/l94FHLiskQe8twB+uYgcw7u/x8CgcQU=
X-Complaints-To: abuse@comcast.net
X-DMCA-Complaints-To: dmca@comcast.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.1

Reply to Parent Message