Virtual memory implementation in S/370 (a.f.c x-post)

2006-05-12 Thread Richard Corak
The recent thread about virtual memory sparked a (kind of) idle question: why did the implementation in the S/370 have a two-level scheme (segment and page)? My original thought was that it facilitated definition of discontiguous parts of an address space. Well, mostly it is because smaller

Virtual memory implementation in S/370 (a.f.c x-post)

2006-05-11 Thread glen herrmannsfeldt
Marten Kemp [EMAIL PROTECTED] writes: The recent thread about virtual memory sparked a (kind of) idle question: why did the implementation in the S/370 have a two-level scheme (segment and page)? My original thought was that it facilitated definition of discontiguous parts of an address

Re: Virtual memory implementation in S/370 (a.f.c x-post)

2006-05-11 Thread Alan Ackerman
On Thu, 11 May 2006 11:08:56 -0700, glen herrmannsfeldt [EMAIL PROTECTED] .edu wrote: Marten Kemp [EMAIL PROTECTED] writes: The recent thread about virtual memory sparked a (kind of) idle question: why did the implementation in the S/370 have a two-level scheme (segment and page)? My original

Virtual memory implementation in S/370 (a.f.c x-post)

2006-05-10 Thread Anne Lynn Wheeler
Marten Kemp [EMAIL PROTECTED] writes: The recent thread about virtual memory sparked a (kind of) idle question: why did the implementation in the S/370 have a two-level scheme (segment and page)? My original thought was that it facilitated definition of discontiguous parts of an address

Virtual memory implementation in S/370 (a.f.c x-post)

2006-05-10 Thread Anne Lynn Wheeler
Marten Kemp [EMAIL PROTECTED] writes: The recent thread about virtual memory sparked a (kind of) idle question: why did the implementation in the S/370 have a two-level scheme (segment and page)? My original thought was that it facilitated definition of discontiguous parts of an address