commit-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

hurd-l4/doc vmm.tex


From: Neal H. Walfield
Subject: hurd-l4/doc vmm.tex
Date: Thu, 23 Oct 2003 08:15:47 -0400

CVSROOT:        /cvsroot/hurd
Module name:    hurd-l4
Branch:         
Changes by:     Neal H. Walfield <address@hidden>       03/10/23 08:15:46

Modified files:
        doc            : vmm.tex 

Log message:
        Fix the introduction to containers.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd-l4/doc/vmm.tex.diff?tr1=1.8&tr2=1.9&r1=text&r2=text

Patches:
Index: hurd-l4/doc/vmm.tex
diff -u hurd-l4/doc/vmm.tex:1.8 hurd-l4/doc/vmm.tex:1.9
--- hurd-l4/doc/vmm.tex:1.8     Wed Oct 22 21:22:07 2003
+++ hurd-l4/doc/vmm.tex Thu Oct 23 08:15:46 2003
@@ -319,10 +319,12 @@
 integers identifying \keyword{virtual frame}s in the physical memory
 server.  A virtual frame references a physical frame but is not bound
 to a particular physical frame (this allows the physical memory server
-to move the contents of frames around).  Multiple physical frames may
-reference the same physical frame in which case the memory is shared.
-Sharing may be either real, e.g. System V shared memory, or logical,
-e.g. copy on write.
+to move the contents of frames around).  Virtual frames are the
+sharing mechanism for physical frames.  Although virtual frames may
+not be copied, they may be logically copied thereby creating a new
+virtual frame with the same underlying physical frame in which case
+the physical memory is shared.  Sharing may be either real,
+e.g. System V shared memory, or logical, e.g. copy on write.
 
 When a virtual frame is allocated into a container, there may be no
 physical frame associated with it.  The physical memory server




reply via email to

[Prev in Thread] Current Thread [Next in Thread]