(I wrote)
VAX uses a two level system where page tables are paged.
There is kernel space, which isn't paged and holds the first
level tables referencing pagable second level tables.
z/Archtecture has three levels.
(someone else wrote)
Actually, z/Architecture has 5 levels. So far,
the
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
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
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
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:
http://www.garlic.com/~lynn/2006i.html#22 virtual memory
http://www.garlic.com/~lynn/2006i.html#23 Virtual memory implementation in
S/370
i had also done page migration as well as table migration ... which
were released in my resource manager product ... the blue letter
product announcement
