[src/trunk]: src/share/man/man4/man4.x86 Spelling, sort sections.

[wiz <wiz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/a8a8069bdbe6
branches:  trunk
changeset: 764403:a8a8069bdbe6
user:      wiz <wiz%NetBSD.org@localhost>
date:      Wed Apr 20 08:20:16 2011 +0000

description:
Spelling, sort sections.

diffstat:

 share/man/man4/man4.x86/balloon.4 |  88 +++++++++++++++++++-------------------
 1 files changed, 44 insertions(+), 44 deletions(-)

diffs (126 lines):

diff -r fcbec994c590 -r a8a8069bdbe6 share/man/man4/man4.x86/balloon.4
--- a/share/man/man4/man4.x86/balloon.4 Wed Apr 20 00:21:34 2011 +0000
+++ b/share/man/man4/man4.x86/balloon.4 Wed Apr 20 08:20:16 2011 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: balloon.4,v 1.5 2011/04/20 00:21:34 jym Exp $
+.\"    $NetBSD: balloon.4,v 1.6 2011/04/20 08:20:16 wiz Exp $
 .\"
 .\" Copyright (c) 2011 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -64,7 +64,7 @@
 .Xr xm 1 .
 Alternatively, the host's administrator is free to request to a particular
 domain to give some memory back.
-This command requires the targetted domain's cooperation and requires
+This command requires the targeted domain's cooperation and requires
 .Nm balloon
 support within it.
 This can be done through the
@@ -107,10 +107,29 @@
 This entry serves the same purpose as the
 .Dq memory/target
 entry in Xenstore.
-This controls the targetted number of pages that the domain should have.
+This controls the targeted number of pages that the domain should have.
 Note that this is only a target, and may not be achieved for a variety of
 reasons.
 .El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "WARNING: balloon could not reach target %zu (current %zu)"
+.Nm
+failed to reach the target reservation.
+This is typically due to a target set too low; the kernel prevented
+memory exhaustion by refusing further allocation.
+.It "increase reservation incomplete: was %zu, returned %d"
+The hypervisor only gave a partial set of memory pages to domain.
+This happens when host's memory consumption is high, and hypervisor
+is unable to give enough free pages back to domain.
+.It "memory 'hot-plug' unsupported - clipping reservation %zu => %zu pages."
+An attempt was made by domain to get more memory than initially obtained
+during boot.
+As physical memory pages cannot be added to memory management sub-system
+dynamically,
+.Nm
+will limit reservation up to the maximum value it can handle.
+.El
 .Sh ERRORS
 When setting the minimum threshold or target reservation entries through
 .Dq kern.xen.balloon ,
@@ -129,47 +148,6 @@
 is above maximum value
 .Pc .
 .El
-.Sh BUGS
-There are a number of reasons why a domain may not attain the targetted
-memory reservation:
-.Nm
-can be empty and cannot be collapsed further, domain
-may not have enough free memory pages (due to memory fragmentation,
-memory exhaustion, ...) so it cannot give enough back to
-.Nm .
-.Pp
-Currently, the virtual memory sub-system of
-.Nx
-is not capable of ``hot-plugging'' new memory pages into place.
-This means that increasing a domain's memory reservation above
-its initial maximum value is pointless, as new memory pages
-cannot be consumed by the memory management sub-system.
-.Pp
-Over expanding
-.Nm
-generates high kernel memory pressure.
-While the driver tries to stay as conservative as possible to avoid
-crashes, a very low memory reservation will lead to unwanted swap or even
-.Fn panic .
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "WARNING: balloon could not reach target %zu (current %zu)"
-.Nm
-failed to reach the target reservation.
-This is typically due to a target set too low; the kernel prevented
-memory exhaustion by refusing further allocation.
-.It "increase reservation incomplete: was %zu, returned %d"
-The hypervisor only gave a partial set of memory pages to domain.
-This happens when host's memory consumption is high, and hypervisor
-is unable to give enough free pages back to domain.
-.It "memory 'hot-plug' unsupported - clipping reservation %zu => %zu pages."
-An attempt was made by domain to get more memory than initially obtained
-during boot.
-As physical memory pages cannot be added to memory management sub-system
-dynamically,
-.Nm
-will limit reservation up to the maximum value it can handle.
-.El
 .Sh SEE ALSO
 .Xr xm 1 ,
 .Xr xenbus 4 ,
@@ -197,6 +175,28 @@
 .An Cherry G. Mathew Aq cherry%NetBSD.org@localhost
 and
 .An Jean-Yves Migeon Aq jym%NetBSD.org@localhost .
+.Sh BUGS
+There are a number of reasons why a domain may not attain the targeted
+memory reservation:
+.Nm
+can be empty and cannot be collapsed further, domain
+may not have enough free memory pages (due to memory fragmentation,
+memory exhaustion, ...) so it cannot give enough back to
+.Nm .
+.Pp
+Currently, the virtual memory sub-system of
+.Nx
+is not capable of ``hot-plugging'' new memory pages into place.
+This means that increasing a domain's memory reservation above
+its initial maximum value is pointless, as new memory pages
+cannot be consumed by the memory management sub-system.
+.Pp
+Over expanding
+.Nm
+generates high kernel memory pressure.
+While the driver tries to stay as conservative as possible to avoid
+crashes, a very low memory reservation will lead to unwanted swap or even
+.Fn panic .
 .Sh SECURITY CONSIDERATIONS
 Ballooning involves moving pages between different domains.
 This includes their content, which can lead to information leak.