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

Fix a typo (duplicated "when you").

Browse source 
PR:		24567
Submitted by:	Robert Drehmel <robert@gizmo.quizbot.org>
This commit is contained in:
Ben Smithurst 2001-01-24 11:50:30 +00:00
parent b74a6fda22
commit 34f100d8e2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=8729
2 changed files with 4 additions and 4 deletions
en_US.ISO8859-1/articles/vm-design
article.sgml
en_US.ISO_8859-1/articles/vm-design
article.sgml

4
en_US.ISO8859-1/articles/vm-design/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/vm-design/article.sgml,v 1.1 2000/10/08 19:23:10 nik Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/vm-design/article.sgml,v 1.2 2000/10/23 14:42:50 nik Exp $ -->
<!-- FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
@ -258,7 +258,7 @@
<para>This model creates a number of potential problems. The first is that
you can wind up with a relatively deep stack of layered VM Objects which
can cost scanning time and memory when you when you take a fault. Deep
can cost scanning time and memory when you take a fault. Deep
layering can occur when processes fork and then fork again (either
parent or child). The second problem is that you can wind up with dead,
inaccessible pages deep in the stack of VM Objects. In our last example

4
en_US.ISO_8859-1/articles/vm-design/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/vm-design/article.sgml,v 1.1 2000/10/08 19:23:10 nik Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/vm-design/article.sgml,v 1.2 2000/10/23 14:42:50 nik Exp $ -->
<!-- FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
@ -258,7 +258,7 @@
<para>This model creates a number of potential problems. The first is that
you can wind up with a relatively deep stack of layered VM Objects which
can cost scanning time and memory when you when you take a fault. Deep
can cost scanning time and memory when you take a fault. Deep
layering can occur when processes fork and then fork again (either
parent or child). The second problem is that you can wind up with dead,
inaccessible pages deep in the stack of VM Objects. In our last example