Move mmap consistency FAQ into assignment description.

diff --git a/doc/vm.texi b/doc/vm.texi
index 0f6fa4f9a95a57fcebbd1c6e02056d0bbfd9b7e9..2c967472e3a873bf9ce1472cb2012cb4775ac223 100644 (file)
--- a/doc/vm.texi
+++ b/doc/vm.texi
@@ -556,6 +556,12 @@ implicitly or explicitly, all pages written to by the process are
 written back to the file, and pages not written must not be.  The pages
 are then removed from the process's list of virtual pages.
 
+If two or more processes map the same file, there is no requirement that
+they see consistent data.  Unix handles this by making the two mappings
+share the same physical page, but the @code{mmap} system call also has
+an argument allowing the client to specify whether the page is shared or
+private (i.e.@: copy-on-write).
+
 @node Project 3 FAQ
 @section FAQ
 
@@ -785,14 +791,6 @@ munmap (map);
 The @command{mcp} program in @file{src/examples} shows how to copy a
 file using memory-mapped I/O.
 
-@item What if two processes map the same file into memory?
-
-There is no requirement in Pintos that the two processes see
-consistent data.  Unix handles this by making the two mappings share the
-same physical page, but the @code{mmap} system call also has an
-argument allowing the client to specify whether the page is shared or
-private (i.e.@: copy-on-write).
-
 @item What happens if a user removes a @code{mmap}'d file?
 
 The mapping should remain valid, following the Unix convention.