--- a/usr/src/man/man7/FSS.7	Wed Aug 22 11:46:01 2018 -0600
+++ b/usr/src/man/man7/FSS.7	Tue Dec 17 18:19:26 2019 -0600
@@ -1,165 +1,190 @@
-'\" te
 .\" Copyright (c) 2001, Sun Microsystems, Inc. All Rights Reserved
-.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
-.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH FSS 7 "May 13, 2017"
-.SH NAME
-FSS \- Fair share scheduler
-.SH DESCRIPTION
-.LP
+.\" Copyright 2019 Joyent, Inc.
+.\"
+.\" The contents of this file are subject to the terms of the
+.\" Common Development and Distribution License (the "License").
+.\" You may not use this file except in compliance with the License.
+.\"
+.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
+.\" or http://www.opensolaris.org/os/licensing.
+.\" See the License for the specific language governing permissions
+.\" and limitations under the License.
+.\"
+.\" When distributing Covered Code, include this CDDL HEADER in each
+.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
+.\" If applicable, add the following below this CDDL HEADER, with the
+.\" fields enclosed by brackets "[]" replaced with your own identifying
+.\" information: Portions Copyright [yyyy] [name of copyright owner]
+.\"
+.Dd December 17, 2019
+.Dt FSS 7
+.Os
+.Sh NAME
+.Nm FSS
+.Nd Fair share scheduler
+.Sh DESCRIPTION
 The fair share scheduler (FSS) guarantees application performance by explicitly
-allocating shares of CPU resources to projects. A share indicates a project's
-entitlement to available CPU resources. Because shares are meaningful only in
+allocating shares of CPU resources to projects.
+A share indicates a project's
+entitlement to available CPU resources.
+Because shares are meaningful only in
 comparison with other project's shares, the absolute quantity of shares is not
-important. Any number that is in proportion with the desired CPU entitlement
+important.
+Any number that is in proportion with the desired CPU entitlement
 can be used.
-.sp
-.LP
+.Pp
 The goals of the FSS scheduler differ from the traditional time-sharing
-scheduling class (TS). In addition to scheduling individual LWPs, the FSS
+scheduling class (TS).
+In addition to scheduling individual LWPs, the FSS
 scheduler schedules projects against each other, making it impossible for any
 project to acquire more CPU cycles simply by running more processes
 concurrently.
-.sp
-.LP
+.Pp
 A project's entitlement is individually calculated by FSS independently for
-each processor set if the project contains processes bound to them. If a
+each processor set if the project contains processes bound to them.
+If a
 project is running on more than one processor set, it can have different
-entitlements on every set. A project's entitlement is defined as a ratio
+entitlements on every set.
+A project's entitlement is defined as a ratio
 between the number of shares given to a project and the sum of shares of all
-active projects running on the same processor set. An active project is one
-that has at least one running or runnable process. Entitlements are recomputed
+active projects running on the same processor set.
+An active project is one
+that has at least one running or runnable process.
+Entitlements are recomputed
 whenever any project becomes active or inactive, or whenever the number of
 shares is changed.
-.sp
-.LP
+.Pp
 Processor sets represent virtual machines in the FSS scheduling class and
-processes are scheduled independently in each processor set. That is, processes
+processes are scheduled independently in each processor set.
+That is, processes
 compete with each other only if they are running on the same processor set.
 When a processor set is destroyed, all processes that were bound to it are
-moved to the default processor set, which always exists. Empty processor sets
+moved to the default processor set, which always exists.
+Empty processor sets
 (that is, sets without processors in them) have no impact on the FSS scheduler
 behavior.
-.sp
-.LP
+.Pp
 If a processor set contains a mix of TS/IA and FSS processes, the fairness of
 the FSS scheduling class can be compromised because these classes use the same
-range of priorities. Fairness is most significantly affected if processes
+range of priorities.
+Fairness is most significantly affected if processes
 running in the TS scheduling class are CPU-intensive and are bound to
-processors within the processor set. As a result, you should avoid having
-processes from TS/IA and FSS classes share the same processor set. RT and FSS
+processors within the processor set.
+As a result, you should avoid having
+processes from TS/IA and FSS classes share the same processor set.
+RT and FSS
 processes use disjoint priority ranges and therefore can share processor sets.
-.sp
-.LP
-As projects execute, their CPU usage is accumulated over time. The FSS
+.Pp
+As projects execute, their CPU usage is accumulated over time.
+The FSS
 scheduler periodically decays CPU usages of every project by multiplying it
 with a decay factor, ensuring that more recent CPU usage has greater weight
-when taken into account for scheduling. The FSS scheduler continually adjusts
+when taken into account for scheduling.
+The FSS scheduler continually adjusts
 priorities of all processes to make each project's relative CPU usage converge
 with its entitlement.
-.sp
-.LP
+.Pp
 While FSS is designed to fairly allocate cycles over a long-term time period,
 it is possible that projects will not receive their allocated shares worth of
-CPU cycles due to uneven demand. This makes one-shot, instantaneous analysis of
+CPU cycles due to uneven demand.
+This makes one-shot, instantaneous analysis of
 FSS performance data unreliable.
-.sp
-.LP
-Note that share is not the same as utilization. A project may be allocated 50%
-of the system, although on the average, it uses just 20%. Shares serve to cap a
+.Pp
+Note that share is not the same as utilization.
+A project may be allocated 50%
+of the system, although on the average, it uses just 20%.
+Shares serve to cap a
 project's CPU usage only when there is competition from other projects running
-on the same processor set. When there is no competition, utilization may be
-larger than entitlement based on shares. Allocating a small share to a busy
+on the same processor set.
+When there is no competition, utilization may be
+larger than entitlement based on shares.
+Allocating a small share to a busy
 project slows it down but does not prevent it from completing its work if the
 system is not saturated.
-.sp
-.LP
+.Pp
 The configuration of CPU shares is managed by the name server as a property of
-the \fBproject\fR(4) database. In the following example, an entry in the
-\fB/etc/project\fR file sets the number of shares for project \fBx-files\fR to
-10:
-.sp
-.in +2
-.nf
+the
+.Xr project 4
+database.
+In the following example, an entry in the
+.Pa /etc/project
+file sets the number of shares for project
+.Sy x-files
+to 10:
+.Bd -literal -offset 2n
 x-files:100::::project.cpu-shares=(privileged,10,none)
-.fi
-.in -2
-
-.sp
-.LP
-Projects with undefined number of shares are given one share each. This means
-that such projects are treated with equal importance. Projects with 0 shares
+.Ed
+.Pp
+Projects with undefined number of shares are given one share each.
+This means
+that such projects are treated with equal importance.
+Projects with 0 shares
 only run when there are no projects with non-zero shares competing for the same
-processor set. The maximum number of shares that can be assigned to one project
+processor set.
+The maximum number of shares that can be assigned to one project
 is 65535.
-.sp
-.LP
-You can use the \fBprctl\fR(1) command to determine the current share
+.Pp
+You can use the
+.Xr prctl 1
+command to determine the current share
 assignment for a given project:
-.sp
-.in +2
-.nf
+.Bd -literal -offset 2n
 $ prctl -n project.cpu-shares -i project x-files
-.fi
-.in -2
-
-.sp
-.LP
+.Ed
+.Pp
 or to change the amount of shares if you have root privileges:
-.sp
-.in +2
-.nf
+.Bd -literal -offset 2n
 # prctl -r -n project.cpu-shares -v 5 -i project x-files
-.fi
-.in -2
-
-.sp
-.LP
-See the \fBprctl\fR(1) man page for additional information on how to modify and
+.Ed
+.Pp
+See the
+.Xr prctl 1
+man page for additional information on how to modify and
 examine resource controls associated with active processes, tasks, or projects
-on the system. See \fBresource_controls\fR(5) for a description of the resource
+on the system.
+See
+.Xr resource_controls 5
+for a description of the resource
 controls supported in the current release of the Solaris operating system.
-.sp
-.LP
-By default, project \fBsystem\fR (project ID 0) includes all system daemons
-started by initialization scripts and has an "unlimited" amount of shares. That
+.Pp
+By default, project
+.Sy system
+(project ID 0) includes all system daemons
+started by initialization scripts and has an
+.Dq unlimited
+amount of shares.
+That
 is, it is always scheduled first no matter how many shares are given to other
 projects.
-.sp
-.LP
+.Pp
 The following command sets FSS as the default scheduler for the system:
-.sp
-.in +2
-.nf
+.Bd -literal -offset 2n
 # dispadmin -d FSS
-.fi
-.in -2
-
-.sp
-.LP
-This change will take effect on the next reboot. Alternatively, you can move
+.Ed
+.Pp
+This change will take effect on the next reboot.
+Alternatively, you can move
 processes from the time-share scheduling class (as well as the special case of
 init) into the FSS class without changing your default scheduling class and
-rebooting by becoming \fBroot\fR, and then using the \fBpriocntl\fR(1) command,
-as shown in the following example:
-.sp
-.in +2
-.nf
+rebooting by becoming
+.Sy root ,
+and then using the
+.Xr priocntl 1
+command, as shown in the following example:
+.Bd -literal -offset 2n
 # priocntl -s -c FSS -i class TS
 # priocntl -s -c FSS -i pid 1
-.fi
-.in -2
-
-.SH CONFIGURING SCHEDULER WITH DISPADMIN
-.LP
-You can use the \fBdispadmin\fR(1M) command to examine and tune the FSS
-scheduler's time quantum value. Time quantum is the amount of time that a
-thread is allowed to run before it must relinquish the processor. The following
+.Ed
+.Sh CONFIGURING SCHEDULER WITH DISPADMIN
+You can use the
+.Xr dispadmin 1M
+command to examine and tune the FSS
+scheduler's time quantum value.
+Time quantum is the amount of time that a
+thread is allowed to run before it must relinquish the processor.
+The following
 example dumps the current time quantum for the fair share scheduler:
-.sp
-.in +2
-.nf
+.Bd -literal -offset 2n
 $ dispadmin -g -c FSS
 	#
 	# Fair Share Scheduler Configuration
@@ -169,32 +194,38 @@
 	# Time Quantum
 	#
 	QUANTUM=110
-.fi
-.in -2
-
-.sp
-.LP
+.Ed
+.Pp
 The value of the QUANTUM represents some fraction of a second with the
-fractional value determined by the reciprocal value of RES. With the default
-value of RES = 1000, the reciprocal of 1000 is .001, or milliseconds. Thus, by
+fractional value determined by the reciprocal value of RES.
+With the default
+value of RES = 1000, the reciprocal of 1000 is \&.001, or milliseconds.
+Thus, by
 default, the QUANTUM value represents the time quantum in milliseconds.
-.sp
-.LP
-If you change the RES value using \fBdispadmin\fR with the \fB-r\fR option, you
-also change the QUANTUM value. For example, instead of quantum of 110 with RES
-of 1000, a quantum of 11 with a RES of 100 results. The fractional unit is
-different while the amount of time is the same.
-.sp
-.LP
-You can use the \fB-s\fR option to change the time quantum value. Note that
-such changes are not preserved across reboot. Please refer to the
-\fBdispadmin\fR(1M) man page for additional information.
-
-.SH SEE ALSO
-.LP
-\fBprctl\fR(1), \fBpriocntl\fR(1), \fBdispadmin\fR(1M), \fBpsrset\fR(1M),
-\fBpriocntl\fR(2), \fBproject\fR(4), \fBresource_controls\fR(5)
-.sp
-.LP
-\fISystem Administration Guide:  Virtualization Using the Solaris Operating
-System\fR
+.Pp
+If you change the RES value using
+.Xr dispadmin 1M
+with the
+.Fl r
+option, you also change the QUANTUM value.
+For example, instead of quantum of 110 with RES
+of 1000, a quantum of 11 with a RES of 100 results.
+The fractional unit is different while the amount of time is the same.
+.Pp
+You can use the
+.Fl s
+option to change the time quantum value.
+Note that such changes are not preserved across reboot.
+Please refer to the
+.Xr dispadmin 1M
+man page for additional information.
+.Sh SEE ALSO
+.Xr prctl 1 ,
+.Xr priocntl 1 ,
+.Xr dispadmin 1M ,
+.Xr psrset 1M ,
+.Xr priocntl 2 ,
+.Xr project 4 ,
+.Xr resource_controls 5
+.Pp
+.%T System Administration Guide: Virtualization Using the Solaris Operating System

--- a/usr/src/man/man7/Intro.7	Wed Aug 22 11:46:01 2018 -0600
+++ b/usr/src/man/man7/Intro.7	Tue Dec 17 18:19:26 2019 -0600
@@ -1,173 +1,209 @@
-'\" te
 .\" Copyright (c) 1999, Sun Microsystems, Inc.  All Rights Reserved.
 .\" Copyright 1989 AT&T
-.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
-.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH INTRO 7 "Sep 29, 1994"
-.SH NAME
-Intro, intro \- introduction to special files
-.SH DESCRIPTION
-.sp
-.LP
-This section describes various device and network interfaces  available on the
-system.  The types of interfaces described  include character and block
-devices, STREAMS modules, network protocols, file systems, and ioctl requests
+.\" Copyright 2020 Joyent, Inc.
+.\"
+.\" The contents of this file are subject to the terms of the
+.\" Common Development and Distribution License (the "License").
+.\" You may not use this file except in compliance with the License.
+.\"
+.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
+.\" or http://www.opensolaris.org/os/licensing.
+.\" See the License for the specific language governing permissions
+.\" and limitations under the License.
+.\"
+.\" When distributing Covered Code, include this CDDL HEADER in each
+.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
+.\" If applicable, add the following below this CDDL HEADER, with the
+.\" fields enclosed by brackets "[]" replaced with your own identifying
+.\" information: Portions Copyright [yyyy] [name of copyright owner]
+.\"
+.Dd January  6, 2020
+.Dt INTRO 7
+.Os
+.Sh NAME
+.Nm Intro ,
+.Nm intro
+.Nd introduction to special files
+.Sh DESCRIPTION
+This section describes various device and network interfaces available on the
+sysstem.
+The types of interfaces described include character and block
+devices,
+.Sy STREAMS
+modules, network protocols, file systems, and ioctl requests
 for driver subsystems and classes.
-.sp
-.LP
+.Pp
 This section contains the following major collections:
-.sp
-.ne 2
-.na
-\fB(7D)\fR
-.ad
-.RS 9n
+.Bl -tag -width "xxxxx"
+.It Pq Sy 7D
 The system provides drivers for a variety of hardware devices, such as disk,
-magnetic tapes, serial communication lines, mice, and frame  buffers, as well
+magnetic tapes, serial communication lines, mice, and frame buffers, as well
 as virtual devices such as pseudo-terminals and windows.
-.sp
+.Pp
 This section describes special files that refer to specific hardware
-peripherals and device drivers. STREAMS   device drivers are also described.
+peripherals and device drivers.
+.Sy STREAMS
+device drivers are also described.
 Characteristics of both the hardware device and the corresponding device driver
 are discussed where applicable.
-.sp
-An application accesses a device through that device's special file. This
+.Pp
+An application accesses a device through that device's special file.
+This
 section specifies the device special file to be used to access the device as
 well as application programming interface (API) information relevant to the use
 of the device driver.
-.sp
-All device special files are located under the  \fB/devices\fR directory.  The
-\fB/devices\fR directory hierarchy attempts to mirror the hierarchy of system
-busses, controllers, and devices configured on the system.   Logical device
-names for special files in \fB/devices\fR are located under the  \fB/dev\fR
-directory. Although not every special file under \fB/devices\fR will have a
-corresponding logical entry under  \fB/dev\fR, whenever possible, an
-application should reference a device using  the logical name for the device.
-Logical device names are listed in the  \fBFILES\fR section of the page for the
-device in question.
-.sp
-This section also describes driver configuration where applicable. Many device
-drivers have a driver configuration file of the form
-\fIdriver_name\fR\fB\&.conf\fR associated with them (see
-\fBdriver.conf\fR(4)). The configuration information stored  in the driver
-configuration file is used to configure the driver and the device.  Driver
-configuration files are located in  \fB/kernel/drv\fR and
-\fB/usr/kernel/drv\fR. Driver configuration files for platform dependent
-drivers are  located in \fB/platform/`uname\fR \fB-i`/kernel/drv\fR where
-\fB`uname\fR \fB-i`\fR is the output of the  \fBuname\fR(1) command with the
-\fB-i\fR option.
-.sp
-Some driver configuration files may contain user configurable  properties.
+All device special files are located under the
+.Pa /devices
+directory.
+The
+.Pa /devices
+directory hierarchy attempts to mirror the hierarchy of system
+busses, controllers, and devices configured on the system.
+Logical device names for special files in
+.Pa /devices
+are located under the
+.Pa /dev
+directory.
+Although not every special file under
+.Pa /devices
+will have a corresponding logical entry under
+.Pa /dev ,
+whenever possible, an
+application should reference a device using the logical name for the device.
+Logical device names are listed in the
+.Sy FILES
+section of the page for the device in question.
+.Pp
+This section also describes driver configuration where applicable.
+Many device drivers have a driver configuration file of the form
+.Em driver_name Ns \&.conf
+associated with them (see
+.Xr driver.conf 4 ) .
+The configuration information stored in the driver
+configuration file is used to configure the driver and the device.
+Driver configuration files are located in
+.Pa /kernel/drv
+and
+.Pa /usr/kernel/drv .
+Driver configuration files for platform dependent
+drivers are located in
+.Pa /platform/`uname\ -i`/kernel/drv
+where
+.Pa `uname\ -i`
+is the output of the
+.Xr uname 1
+command with the
+.Fl i
+option.
+.Pp
+Some driver configuration files may contain user configurable properties.
 Changes in a driver's configuration file will not take effect until the system
-is rebooted or the driver has been removed and re-added (see  \fBrem_drv\fR(1M)
-and  \fBadd_drv\fR(1M)).
-.RE
-
-.sp
-.ne 2
-.na
-\fB(7FS)\fR
-.ad
-.RS 9n
-This section describes the  programmatic interface for several file systems
+is rebooted or the driver has been removed and re-added (see
+.Xr rem_drv 1M
+and
+.Xr add_drv 1M ) .
+.It Pq Sy 7FS
+This section describes the programmatic interface for several file systems
 supported by SunOS.
-.RE
-
-.sp
-.ne 2
-.na
-\fB(7I)\fR
-.ad
-.RS 9n
+.It Pq Sy 7I
 This section describes ioctl requests which apply to a class of drivers or
-subsystems. For example, ioctl requests which apply to most tape devices are
-discussed in  \fBmtio\fR(7I). Ioctl requests relevant to only a specific
-device are described on the man page for that device. The page for the device
+subsystems.
+For example, ioctl requests which apply to most tape devices are
+discussed in
+.Xr mtio 7I .
+Ioctl requests relevant to only a specific
+device are described on the man page for that device.
+The page for the device
 in question should still be examined for exceptions to the ioctls listed in
 section 7I.
-.RE
-
-.sp
-.ne 2
-.na
-\fB(7M)\fR
-.ad
-.RS 9n
-This section describes  \fBSTREAMS\fR modules.  Note that  \fBSTREAMS\fR
-drivers are discussed in section 7D. \fBstreamio\fR(7I) contains a list of
-ioctl requests used to manipulate \fBSTREAMS\fR modules and interface with the
-\fBSTREAMS\fR framework.  Ioctl requests specific to a  \fBSTREAMS\fR module
-will be discussed on the man page for that module.
-.RE
-
-.sp
-.ne 2
-.na
-\fB(7P)\fR
-.ad
-.RS 9n
+.It Pq Sy 7M
+This section describes
+.Sy STREAMS
+modules.
+Note that
+.Sy STREAMS
+drivers are discussed in section 7D.
+.Xr streamio 7I
+contains a list of ioctl requests used to manipulate
+.Sy STREAMS
+modules and interface with the
+.Sy STREAMS
+framework.
+.Xr ioctl 2
+requests specific to a
+.Sy STREAMS
+module will be discussed on the man page for that module.
+.It Pq Sy 7P
 This section describes various network protocols available in SunOS.
-.sp
-SunOS supports both socket-based and \fBSTREAMS-based\fR network
-communications. The Internet protocol family, described in \fBinet\fR(7P), is
-the primary protocol family supported by SunOS, although the system can support
-a number of others.  The raw interface provides low-level services, such as
+SunOS supports both socket-based and
+.Sy STREAMS Ns -based
+network communications.
+.Pp
+The Internet protocol family, described in
+.Xr inet 7P ,
+is the primary protocol family supported by SunOS, although the system can
+support a number of others.
+The raw interface provides low-level services, such as
 packet fragmentation and reassembly, routing, addressing, and basic transport
-for socket-based implementations.  Facilities for communicating using an
-Internet-family protocol are generally accessed by specifying the \fBAF_INET\fR
-address family when binding a socket; see \fBsocket\fR(3SOCKET) for details.
-.sp
+for socket-based implementations.
+Facilities for communicating using an
+Internet-family protocol are generally accessed by specifying the
+.Dv AF_INET
+address family when binding a socket; see
+.Xr socket 3SOCKET
+for details.
+.Pp
 Major protocols in the Internet family include:
-.RS +4
-.TP
-.ie t \(bu
-.el o
+.Bl -bullet -offset indent
+.It
 The Internet Protocol (IP) itself, which supports the universal datagram
-format, as described in \fBip\fR(7P). This is the default protocol for
-\fBSOCK_RAW\fR type sockets within the \fBAF_INET\fR domain.
-.RE
-.RS +4
-.TP
-.ie t \(bu
-.el o
-The Transmission Control Protocol (TCP); see \fBtcp\fR(7P). This is the default
-protocol for \fBSOCK_STREAM\fR type sockets.
-.RE
-.RS +4
-.TP
-.ie t \(bu
-.el o
-The User Datagram Protocol (UDP); see \fBudp\fR(7P). This is the default
-protocol for \fBSOCK_DGRAM\fR type sockets.
-.RE
-.RS +4
-.TP
-.ie t \(bu
-.el o
-The Address Resolution Protocol (ARP); see \fBarp\fR(7P).
-.RE
-.RS +4
-.TP
-.ie t \(bu
-.el o
-The Internet Control Message Protocol (ICMP); see \fBicmp\fR(7P).
-.RE
-.RE
-
-.SH SEE ALSO
-.sp
-.LP
-\fBadd_drv\fR(1M), \fBrem_drv\fR(1M), \fBIntro\fR(3), \fBioctl\fR(2),
-\fBsocket\fR(3SOCKET), \fBdriver.conf\fR(4), \fBarp\fR(7P), \fBicmp\fR(7P),
-\fBinet\fR(7P), \fBip\fR(7P), \fBmtio\fR(7I), \fBst\fR(7D), \fBstreamio\fR(7I),
-\fBtcp\fR(7P), \fBudp\fR(7P)
-.sp
-.LP
-\fISystem Administration Guide: IP Services\fR
-.sp
-.LP
-\fISTREAMS Programming Guide\fR
-.sp
-.LP
-\fIWriting Device Drivers\fR
+format, as described in
+.Xr ip 7P .
+This is the default protocol for
+.Dv SOCK_RAW
+type sockets within the
+.Dv AF_INET
+domain.
+.It
+The Transmission Control Protocol (TCP); see
+.Xr tcp 7P .
+This is the default protocol for
+.Dv SOCK_STREAM
+type sockets.
+.It
+The User Datagram Protocol (UDP); see
+.Xr udp 7P .
+This is the default
+protocol for
+.Dv SOCK_DGRAM
+type sockets.
+.It
+The Address Resolution Protocol (ARP); see
+.Xr arp 7P .
+.It
+The Internet Control Message Protocol (ICMP); see
+.Xr icmp 7P .
+.El
+.El
+.Sh SEE ALSO
+.Xr add_drv 1M ,
+.Xr rem_drv 1M ,
+.Xr ioctl 2 ,
+.Xr Intro 3 ,
+.Xr socket 3SOCKET ,
+.Xr driver.conf 4 ,
+.Xr st 7D ,
+.Xr mtio 7I ,
+.Xr streamio 7I ,
+.Xr arp 7P ,
+.Xr icmp 7P ,
+.Xr inet 7P ,
+.Xr ip 7P ,
+.Xr tcp 7P ,
+.Xr udp 7P
+.Pp
+.%T System Administration Guide: IP Services
+.Pp
+.%T STREAMS Programming Guide
+.Pp
+.%T Writing Device Drivers

--- a/usr/src/man/man7/cpr.7	Wed Aug 22 11:46:01 2018 -0600
+++ b/usr/src/man/man7/cpr.7	Tue Dec 17 18:19:26 2019 -0600
@@ -1,98 +1,114 @@
-'\" te
 .\"  Copyright (c) 2001, Sun Microsystems, Inc.
 .\"  All Rights Reserved
-.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
-.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH CPR 7 "May 13, 2017"
-.SH NAME
-cpr \- Suspend and resume module
-.SH SYNOPSIS
-.LP
-.nf
-\fB/platform/'uname -m'/kernel/misc/cpr\fR
-.fi
-
-.SH DESCRIPTION
-.LP
-The \fBcpr\fR module is a loadable module used to suspend and resume the entire
-system. You may wish to suspend a system to save power or to power off
-temporarily for transport. The \fBcpr\fR module should not be used in place of
+.\"
+.\" Copyright 2020 Joyent, Inc.
+.\"
+.\" The contents of this file are subject to the terms of the
+.\" Common Development and Distribution License (the "License").
+.\" You may not use this file except in compliance with the License.
+.\"
+.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
+.\" or http://www.opensolaris.org/os/licensing.
+.\" See the License for the specific language governing permissions
+.\" and limitations under the License.
+.\"
+.\" When distributing Covered Code, include this CDDL HEADER in each
+.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
+.\" If applicable, add the following below this CDDL HEADER, with the
+.\" fields enclosed by brackets "[]" replaced with your own identifying
+.\" information: Portions Copyright [yyyy] [name of copyright owner]
+.\"
+.Dd January 12, 2020
+.Dt CPR 7
+.Os
+.Sh NAME
+.Nm cpr
+.Nd Suspend and resume module
+.Sh SYNOPSIS
+.Pa /platform/i86pc/kernel/misc/amd64/cpr
+.Pa /platform/sun4u/kernel/misc/sparcv9/cpr
+.Sh DESCRIPTION
+The
+.Nm
+module is a loadable module used to suspend and resume the entire system.
+You may wish to suspend a system to save power or to power off
+temporarily for transport.
+The
+.Nm
+module should not be used in place of
 a normal shutdown when performing any hardware reconfiguration or replacement.
 In order for the resume operation to succeed, it is important that the hardware
-configuration remain the same. When the system is suspended, the entire system
+configuration remain the same.
+When the system is suspended, the entire system
 state is preserved in non-volatile storage until a resume operation is
 conducted.
-.sp
-.LP
-\fBpmconfig\fR(1M) and \fBpower.conf\fR(4) are used to configure the
-suspend-resume feature.
-.sp
-.LP
+.Pp
+.Xr pmconfig 1M
+and
+.Xr power.conf 4
+are used to configure the suspend-resume feature.
+.Pp
 The speed of suspend and resume operations can range from 15 seconds to
 several minutes, depending on the system speed, memory size, and load.
-.sp
-.LP
-During resume operation, the \fBSIGTHAW\fR signal is sent to all processes to
+.Pp
+During resume operation, the
+.Dv SIGTHAW
+signal is sent to all processes to
 allow them to do any special processing in response to suspend-resume
-operation. Normally applications are not required to do any special processing
+operation.
+Normally applications are not required to do any special processing
 because of suspend-resume, but some specialized processes can use
-\fBSIGTHAW\fR to restore the state prior to suspend. For example, \fBX\fR can
-refresh the screen in response to \fBSIGTHAW\fR.
-.sp
-.LP
-In some cases the \fBcpr\fR module may be unable to perform the suspend
-operation. If a system contains additional devices outside the standard shipped
+.Dv SIGTHAW
+to restore the state prior to suspend.
+For example,
+.Sy X
+can refresh the screen in response to
+.Dv SIGTHAW .
+.Pp
+In some cases the
+.Nm
+module may be unable to perform the suspend operation.
+If a system contains additional devices outside the standard shipped
 configuration, it is possible that device drivers for these additional devices
-might not support suspend-resume operations. In this case, the suspend fails
-and an error message is displayed. These devices must be removed or their
-device drivers unloaded for the suspend operation to succeed. Contact the
+might not support suspend-resume operations.
+In this case, the suspend fails and an error message is displayed.
+These devices must be removed or their
+device drivers unloaded for the suspend operation to succeed.
+Contact the
 device manufacturer to obtain a new version of device driver that supports
 suspend-resume.
-.sp
-.LP
+.Pp
 A suspend may also fail when devices or processes are performing critical or
-time-sensitive operations (such as realtime operations). The system will remain
-in its current running state. Messages reporting the failure will be displayed
-on the console and status returned to the caller. Once the system is
+time-sensitive operations (such as realtime operations).
+The system will remain in its current running state.
+Messages reporting the failure will be displayed
+on the console and status returned to the caller.
+Once the system is
 successfully suspended the resume operation will succeed, barring external
 influences such as a hardware reconfiguration.
-.sp
-.LP
+.Pp
 Some network-based applications may fail across a suspend and resume cycle.
 This largely depends on the underlying network protocol and the applications
-involved.  In general, applications that retry and automatically reestablish
+involved.
+In general, applications that retry and automatically reestablish
 connections will continue to operate transparently on a resume operation;
 those applications that do not will likely fail.
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE	ATTRIBUTE VALUE
-_
-Interface stability 	Unstable
-.TE
-
-.SH SEE ALSO
-.LP
-\fBpmconfig\fR(1M),
-\fBuadmin\fR(1M), \fBuadmin\fR(2), \fBpower.conf\fR(4), \fBattributes\fR(5)
-.sp
-.LP
-\fIWriting Device Drivers\fR
-.SH NOTES
-.LP
+.Sh INTERFACE STABILITY
+Unstable
+.Sh SEE ALSO
+.Xr pmconfig 1M ,
+.Xr uadmin 1M ,
+.Xr uadmin 2 ,
+.Xr power.conf 4 ,
+.Xr attributes 5
+.Pp
+.%T Writing Device Drivers
+.Sh NOTES
 Certain device operations such as tape and floppy disk activities are not
-resumable due to the nature of removable media.  These activities are detected
+resumable due to the nature of removable media.
+These activities are detected
 at suspend time, and must be stopped before the suspend operation will
 complete successfully.
-.sp
-.LP
+.Pp
 Suspend-resume is currently supported only on a limited set of hardware
 platforms.

--- a/usr/src/man/man7/ibmf.7	Wed Aug 22 11:46:01 2018 -0600
+++ b/usr/src/man/man7/ibmf.7	Tue Dec 17 18:19:26 2019 -0600
@@ -1,71 +1,47 @@
-'\" te
 .\"  Copyright (c) 2004, Sun Microsystems, Inc.  All Rights Reserved
-.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
-.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH IBMF 7 "Sep 9, 2004"
-.SH NAME
-ibmf \- InfiniBand Management Transport Framework
-.SH DESCRIPTION
-.sp
-.LP
+.\" Copyright 2020 Joyent, Inc.
+.\"
+.\" The contents of this file are subject to the terms of the
+.\" Common Development and Distribution License (the "License").
+.\" You may not use this file except in compliance with the License.
+.\"
+.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
+.\" or http://www.opensolaris.org/os/licensing.
+.\" See the License for the specific language governing permissions
+.\" and limitations under the License.
+.\"
+.\" When distributing Covered Code, include this CDDL HEADER in each
+.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
+.\" If applicable, add the following below this CDDL HEADER, with the
+.\" fields enclosed by brackets "[]" replaced with your own identifying
+.\" information: Portions Copyright [yyyy] [name of copyright owner]
+.\"
+.Dd January 12, 2020
+.Dt IBMF 7
+.Os
+.Sh NAME
+.Nm ibmf
+.Nd InfiniBand Management Transport Framework
+.Sh DESCRIPTION
 The InfiniBand (IB) Management Transport Framework provides the mechanisms for
 IB management modules to communicate with other InfiniBand management modules
-such as the Subnet Administration process.  It also provides helper functions
+such as the Subnet Administration process.
+It also provides helper functions
 such as Subnet Administration Access (SAA) for commonly performed operations.
-.SH FILES
-.sp
-.ne 2
-.na
-\fB/kernel/misc/ibmf\fR
-.ad
-.RS 29n
-32-bit ELF kernel misc module (x86 platform only).
-.RE
-
-.sp
-.ne 2
-.na
-\fB/kernel/misc/amd64/ibmf\fR
-.ad
-.RS 29n
-64-bit ELF kernel misc module (x86 platform only).
-.RE
-
-.sp
-.ne 2
-.na
-\fB/kernel/misc/sparcv9/ibmf\fR
-.ad
-.RS 29n
-64-bit ELF kernel misc module (SPARC platform only).
-.RE
-
-.SH ATTRIBUTES
-.sp
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE	ATTRIBUTE VALUE
-_
-Architecture	PCI-based systems
-_
-Interface stability	Consolidation Private
-.TE
-
-.SH SEE ALSO
-.sp
-.LP
-\fBibtl\fR(7D)
-.sp
-.LP
-\fIInfiniBand Architecture Specification, Version 1.1\fR
-.sp
-.LP
-\fIwww.infinibandta.org\fR
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /kernel/misc/amd64/ibmf
+Device driver (x86).
+.It Pa /kernel/misc/sparcv9/ibmf
+Device driver (SPARC)
+.El
+.Sh ARCHITECTURE
+PCI-based systems
+.Sh INTERFACE STABILITY
+Private
+.Sh SEE ALSO
+.Xr ibtl 7D
+.Pp
+.%T InfiniBand Architecture Specification, Version 1\&.1
+.Pp
+.%U www.infinibandta.org