mdoc style: whitespace fixes.
This commit is contained in:
parent
bd6bb49397
commit
3211796d7f
@ -64,7 +64,6 @@ Managed Object Format (MOF) blob.
|
||||
You can obtain human readable output by bmf2mof in bmfdec tool.
|
||||
(https://github.com/pali/bmfdec)
|
||||
.El
|
||||
|
||||
.Sh EXAMPLES
|
||||
.Bd -literal
|
||||
# cat /dev/wmistat0
|
||||
|
@ -39,7 +39,6 @@ your kernel configuration file:
|
||||
.Cd "device hid"
|
||||
.Cd "device hconf"
|
||||
.Cd "device evdev"
|
||||
|
||||
.Ed
|
||||
.Pp
|
||||
Alternatively, to load the driver as a
|
||||
|
@ -125,7 +125,6 @@ dedicate to the kmem_arena map.
|
||||
The scale value is the ratio of physical to virtual pages.
|
||||
The default value of 3 allocates a page of KVA for each 3 pages
|
||||
of physical ram in the system.
|
||||
|
||||
The kernel and modules, including the root image, also consume KVA.
|
||||
The combination of a large root image and the default scaling
|
||||
may preallocate so much KVA that there is not enough
|
||||
@ -133,7 +132,6 @@ remaining address space to allocate kernel stacks, IO buffers,
|
||||
and other resources that are not part of kmem_arena.
|
||||
Overallocating kmem_arena space is likely to manifest as failure to
|
||||
launch userland processes with "cannot allocate kernel stack" messages.
|
||||
|
||||
Setting the scale value too high may result in kernel failure to allocate
|
||||
memory because kmem_arena is too small, and the failure may require
|
||||
significant runtime to manifest.
|
||||
|
@ -340,7 +340,7 @@ driver will use the drive's recommended timeouts for commands.
|
||||
.Pp
|
||||
The timeouts in use are reported in units of
|
||||
.Sy thousandths
|
||||
of a second via the
|
||||
of a second via the
|
||||
.Va kern.cam.sa.%d.timeout.*
|
||||
.Xr sysctl 8
|
||||
variables.
|
||||
|
@ -100,5 +100,3 @@ first appeared in
|
||||
.Sh AUTHORS
|
||||
.An Neel Natu Aq neel@freebsd.org
|
||||
.An Peter Grehan Aq grehan@freebsd.org
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user