From Newsgroup: comp.arch

In the VMS/WinNT way, each memory section is defined as either shared
or private when created and cannot be changed. This allows optimizations
in page table and page file handling.

Interesting. Do you happen to have a pointer for further reading
about it?

*nix needs to maintain various data structures to support forking
memory just in case it happens.

I can't imagine what those datastructures would be (which might be just
another way to say that I was brought up on POSIX and can't imagine the
world differently).


Stefan
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.arch

Stefan Monnier <monnier@iro.umontreal.ca> writes:

In the VMS/WinNT way, each memory section is defined as either shared
or private when created and cannot be changed. This allows optimizations
in page table and page file handling.

Interesting. Do you happen to have a pointer for further reading
about it?

*nix needs to maintain various data structures to support forking
memory just in case it happens.

I can't imagine what those datastructures would be (which might be just >another way to say that I was brought up on POSIX and can't imagine the
world differently).

http://bitsavers.org/pdf/dec/vax/vms/training/EY-8264E-DP_VMS_Internals_and_Data_Structures_4.4_1988.pdf

--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.arch

Scott Lurndal wrote:

Stefan Monnier <monnier@iro.umontreal.ca> writes:

In the VMS/WinNT way, each memory section is defined as either shared
or private when created and cannot be changed. This allows optimizations >>> in page table and page file handling.

Interesting. Do you happen to have a pointer for further reading
about it?

*nix needs to maintain various data structures to support forking
memory just in case it happens.

I can't imagine what those datastructures would be (which might be just
another way to say that I was brought up on POSIX and can't imagine the
world differently).

http://bitsavers.org/pdf/dec/vax/vms/training/EY-8264E-DP_VMS_Internals_and_Data_Structures_4.4_1988.pdf

Yeah, that's a great book on how VMS works in detail.
My copy is v1.0 from 1981.
It describes the various data structures, some down to the bit level.
Then chapter 15 Paging Dynamics walks through the details of how
paging works.

A book of comparable detail on Linux (but dated) would be:

Understanding the Linux Virtual Memory Manager, Gorman, 2007 https://www.kernel.org/doc/gorman/pdf/understand.pdf

Of a similar nature on Windows but without the detail of the above two is:

(this appears to be two volumes jammed together)
Windows Internals 6th ed vol 1&2, 2012 https://empyreal96.github.io/nt-info-depot/Windows-Internals-PDFs/Windows%20Internals%206e%20Part1%2B2.pdf



--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.arch

EricP <ThatWouldBeTelling@thevillage.com> writes:

Scott Lurndal wrote:

Stefan Monnier <monnier@iro.umontreal.ca> writes:

In the VMS/WinNT way, each memory section is defined as either shared
or private when created and cannot be changed. This allows optimizations >>>> in page table and page file handling.

Interesting. Do you happen to have a pointer for further reading
about it?

*nix needs to maintain various data structures to support forking
memory just in case it happens.

I can't imagine what those datastructures would be (which might be just
another way to say that I was brought up on POSIX and can't imagine the
world differently).

http://bitsavers.org/pdf/dec/vax/vms/training/EY-8264E-DP_VMS_Internals_and_Data_Structures_4.4_1988.pdf

Yeah, that's a great book on how VMS works in detail.
My copy is v1.0 from 1981.

I also have a printed copy from 1981, along with the
internals class notes and the microfiche.


--- Synchronet 3.20a-Linux NewsLink 1.114