[gnome-system-monitor/wip/mallard-help: 60/60] Simplified memory-map-use, reflowed proc-cols

[Ekaterina Gerasimova <egerasimov src gnome org>]

commit 1ef29446b8e692e26fd754703ac801461b46cc1f
Author: Michael Hill <mdhill gnome org>
Date:   Sun Feb 2 23:04:05 2014 +0100

    Simplified memory-map-use, reflowed proc-cols

 help/C/memory-map-use.page  |   44 ++++++++++++++++++++++++++++++++++++++----
 help/C/process-columns.page |    3 +-
 2 files changed, 41 insertions(+), 6 deletions(-)
---
diff --git a/help/C/memory-map-use.page b/help/C/memory-map-use.page
index c823904..6891cd2 100644
--- a/help/C/memory-map-use.page
+++ b/help/C/memory-map-use.page
@@ -31,6 +31,21 @@
     <p>Explain how to use the Memory Map feature.</p>
   </comment>
 
+  <p><gui>Virtual memory</gui> is a representation of the combined
+  <gui>physical memory</gui> and <link xref="mem-swap">swap space</link> in a
+  system. It enables running processes to access <em>more</em> than the
+  existing physical memory by <gui>mapping</gui> locations in physical memory
+  to files on disk. When the system needs more pages of memory than are
+  available, some of the existing pages will be <em>paged out</em> or written
+  to the swap space.</p>
+
+  <p>The <gui>memory map</gui> displays the total virtual memory use of the
+  process, and can be used to determine the memory cost of running a single or
+  multiple instances of the program, to ensure the use of the correct shared
+  libraries, to see the results of adjusting various performance tuning
+  parameters the program may have, or to diagnose issues such as memory
+  leaks.</p>
+
   <p>To display the <link xref="memory-map-what">memory map</link> of a
   process:</p>
 
@@ -84,11 +99,6 @@
          <td><p>The address at which the memory segment ends.</p></td>
   </tr>
   <tr>
-         <td><p>VM Offset</p></td>
-         <td><p>The location of the address within the memory segment, measured from
-    VM Start.</p></td>
-  </tr>
-  <tr>
          <td><p>VM Size</p></td>
          <td><p>The size of the memory segment.</p></td>
   </tr>
@@ -123,6 +133,30 @@
     </td>
   </tr>
   <tr>
+         <td><p>VM Offset</p></td>
+         <td><p>The location of the address within the memory segment,
+    measured from VM Start.</p></td>
+  </tr>
+  <tr>
+         <td><p>Private, Shared, Clean, Dirty</p></td>
+<!--     <td><p>Text pages are flagged read-execute in memory and don't need to
+  be written to swap since they can be re-loaded from their original location
+  on disk. Data pages have read-write permissions, and if modified when in
+  memory, they are labeled <em>dirty</em>, and when designated for swapping,
+  must be paged out.</p></td>
+-->
+          <td><list><item><p><em>private</em> pages are accessed by one
+  process</p></item>
+          <item><p><em>shared</em> pages can be accessed by more than
+  one process</p></item>
+          <item><p><em>clean</em> pages have not yet been modified
+  while in memory and can be discarded when designated to be swapped
+  out</p></item>
+          <item><p><em>dirty</em> pages have been modified while in
+  memory and must be written to disk when designated to be swapped
+  out</p></item></list></td>
+  </tr>
+  <tr>
          <td><p>Device</p></td>
          <td><p>The major and minor numbers of the device on which the shared
     library filename is located. Together these specify a partition on the
diff --git a/help/C/process-columns.page b/help/C/process-columns.page
index 5aa70a1..c486e29 100644
--- a/help/C/process-columns.page
+++ b/help/C/process-columns.page
@@ -36,6 +36,7 @@
 
   <p>For each process listed in the <gui>Processes</gui> tab,
   <app>System Monitor</app> provides information in a number of categories.
-  For detailed descriptions of what the columns mean, check the <link href="man:ps"><cmd>ps</cmd> man 
page</link>.</p>
+  For detailed descriptions of what the columns mean, check the
+  <link href="man:ps"><cmd>ps</cmd> man page</link>.</p>
 
 </page>