os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix the vm chapter layout in order to have a TOC.

Browse source 
Submitted by:	Hiten Pandya <hiten@angelica.unixdaemons.com>
This commit is contained in:
Marc Fonvieille 2002-10-13 16:15:22 +00:00
parent eb3ee3fa6f
commit e2e04c2b7c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14614
2 changed files with 46 additions and 36 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
en_US.ISO8859-1/books/arch-handbook/vm/chapter.sgml
View file

@ -5,14 +5,20 @@
--> -->
<chapter id="vm"> <chapter id="vm">
<chapterinfo>
<authorgroup>
<author>
<firstname>Matthew</firstname>
<surname>Dillon</surname>
<contrib>Contributed by </contrib>
</author>
</authorgroup>
<!-- 6 Feb 1999 -->
</chapterinfo>
<title>Virtual Memory System</title> <title>Virtual Memory System</title>
<sect1 id="internals-vm"> <sect1>
<title>The FreeBSD VM System</title>
<para><emphasis>Contributed by &a.dillon;. 6 Feb 1999</emphasis></para>
<sect2>
<title>Management of physical <title>Management of physical
memory&mdash;<literal>vm_page_t</literal></title> memory&mdash;<literal>vm_page_t</literal></title>
@ -72,9 +78,9 @@
reactivation page faults to determine how active or how idle a page reactivation page faults to determine how active or how idle a page
actually is. This leads to better decisions being made as to when to actually is. This leads to better decisions being made as to when to
launder or swap-out a page.</para> launder or swap-out a page.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>The unified buffer <title>The unified buffer
cache&mdash;<literal>vm_object_t</literal></title> cache&mdash;<literal>vm_object_t</literal></title>
@ -96,9 +102,9 @@
associated with one VM object at a time. The VM object shadowing associated with one VM object at a time. The VM object shadowing
implements the perceived sharing of the same page across multiple implements the perceived sharing of the same page across multiple
instances.</para> instances.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>Filesystem I/O&mdash;<literal>struct buf</literal></title> <title>Filesystem I/O&mdash;<literal>struct buf</literal></title>
<para>vnode-backed VM objects, such as file-backed objects, generally <para>vnode-backed VM objects, such as file-backed objects, generally
@ -131,9 +137,9 @@
limit the amount of concurrent I/O possible. However, as there are usually a limit the amount of concurrent I/O possible. However, as there are usually a
few thousand filesystem buffers available, this is not usually a few thousand filesystem buffers available, this is not usually a
problem.</para> problem.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>Mapping Page Tables - vm_map_t, vm_entry_t</title> <title>Mapping Page Tables - vm_map_t, vm_entry_t</title>
<para>FreeBSD separates the physical page table topology from the VM <para>FreeBSD separates the physical page table topology from the VM
@ -157,9 +163,9 @@
references to the same page in the same object reference the same references to the same page in the same object reference the same
<literal>vm_page_t</literal> and thus give us buffer cache unification <literal>vm_page_t</literal> and thus give us buffer cache unification
across the board.</para> across the board.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>KVM Memory Mapping</title> <title>KVM Memory Mapping</title>
<para>FreeBSD uses KVM to hold various kernel structures. The single <para>FreeBSD uses KVM to hold various kernel structures. The single
@ -179,9 +185,9 @@
constant-sized blocks of memory in order to allocate a specific type constant-sized blocks of memory in order to allocate a specific type
of structure. You can use <command>vmstat -m</command> to get an of structure. You can use <command>vmstat -m</command> to get an
overview of current KVM utilization broken down by zone.</para> overview of current KVM utilization broken down by zone.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>Tuning the FreeBSD VM system</title> <title>Tuning the FreeBSD VM system</title>
<para>A concerted effort has been made to make the FreeBSD kernel <para>A concerted effort has been made to make the FreeBSD kernel
@ -249,7 +255,6 @@ makeoptions COPTFLAGS="-O -pipe"</programlisting>
<para>NFS-based swap is perfectly acceptable on -4.x or later systems, <para>NFS-based swap is perfectly acceptable on -4.x or later systems,
but you must be aware that the NFS server will take the brunt of the but you must be aware that the NFS server will take the brunt of the
paging load.</para> paging load.</para>
</sect2> </sect1>
</sect1>
</chapter> </chapter>

41
en_US.ISO8859-1/books/developers-handbook/vm/chapter.sgml
View file

@ -5,14 +5,20 @@
--> -->
<chapter id="vm"> <chapter id="vm">
<chapterinfo>
<authorgroup>
<author>
<firstname>Matthew</firstname>
<surname>Dillon</surname>
<contrib>Contributed by </contrib>
</author>
</authorgroup>
<!-- 6 Feb 1999 -->
</chapterinfo>
<title>Virtual Memory System</title> <title>Virtual Memory System</title>
<sect1 id="internals-vm"> <sect1>
<title>The FreeBSD VM System</title>
<para><emphasis>Contributed by &a.dillon;. 6 Feb 1999</emphasis></para>
<sect2>
<title>Management of physical <title>Management of physical
memory&mdash;<literal>vm_page_t</literal></title> memory&mdash;<literal>vm_page_t</literal></title>
@ -72,9 +78,9 @@
reactivation page faults to determine how active or how idle a page reactivation page faults to determine how active or how idle a page
actually is. This leads to better decisions being made as to when to actually is. This leads to better decisions being made as to when to
launder or swap-out a page.</para> launder or swap-out a page.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>The unified buffer <title>The unified buffer
cache&mdash;<literal>vm_object_t</literal></title> cache&mdash;<literal>vm_object_t</literal></title>
@ -96,9 +102,9 @@
associated with one VM object at a time. The VM object shadowing associated with one VM object at a time. The VM object shadowing
implements the perceived sharing of the same page across multiple implements the perceived sharing of the same page across multiple
instances.</para> instances.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>Filesystem I/O&mdash;<literal>struct buf</literal></title> <title>Filesystem I/O&mdash;<literal>struct buf</literal></title>
<para>vnode-backed VM objects, such as file-backed objects, generally <para>vnode-backed VM objects, such as file-backed objects, generally
@ -131,9 +137,9 @@
limit the amount of concurrent I/O possible. However, as there are usually a limit the amount of concurrent I/O possible. However, as there are usually a
few thousand filesystem buffers available, this is not usually a few thousand filesystem buffers available, this is not usually a
problem.</para> problem.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>Mapping Page Tables - vm_map_t, vm_entry_t</title> <title>Mapping Page Tables - vm_map_t, vm_entry_t</title>
<para>FreeBSD separates the physical page table topology from the VM <para>FreeBSD separates the physical page table topology from the VM
@ -157,9 +163,9 @@
references to the same page in the same object reference the same references to the same page in the same object reference the same
<literal>vm_page_t</literal> and thus give us buffer cache unification <literal>vm_page_t</literal> and thus give us buffer cache unification
across the board.</para> across the board.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>KVM Memory Mapping</title> <title>KVM Memory Mapping</title>
<para>FreeBSD uses KVM to hold various kernel structures. The single <para>FreeBSD uses KVM to hold various kernel structures. The single
@ -179,9 +185,9 @@
constant-sized blocks of memory in order to allocate a specific type constant-sized blocks of memory in order to allocate a specific type
of structure. You can use <command>vmstat -m</command> to get an of structure. You can use <command>vmstat -m</command> to get an
overview of current KVM utilization broken down by zone.</para> overview of current KVM utilization broken down by zone.</para>
</sect2> </sect1>
<sect2> <sect1>
<title>Tuning the FreeBSD VM system</title> <title>Tuning the FreeBSD VM system</title>
<para>A concerted effort has been made to make the FreeBSD kernel <para>A concerted effort has been made to make the FreeBSD kernel
@ -249,7 +255,6 @@ makeoptions COPTFLAGS="-O -pipe"</programlisting>
<para>NFS-based swap is perfectly acceptable on -4.x or later systems, <para>NFS-based swap is perfectly acceptable on -4.x or later systems,
but you must be aware that the NFS server will take the brunt of the but you must be aware that the NFS server will take the brunt of the
paging load.</para> paging load.</para>
</sect2> </sect1>
</sect1>
</chapter> </chapter>