Index: head/share/man/man4/blackhole.4
===================================================================
--- head/share/man/man4/blackhole.4	(revision 292204)
+++ head/share/man/man4/blackhole.4	(revision 292205)
@@ -1,95 +1,95 @@
 .\"
 .\" blackhole - drop refused TCP or UDP connects
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\"
 .\" $FreeBSD$
 .Dd September 6, 2015
 .Dt BLACKHOLE 4
 .Os
 .Sh NAME
 .Nm blackhole
 .Nd a
 .Xr sysctl 8
 MIB for manipulating behaviour in respect of refused SCTP, TCP, or UDP connection
 attempts
 .Sh SYNOPSIS
 .Cd sysctl net.inet.sctp.blackhole Ns Op = Ns Brq "0 | 1 | 2"
 .Cd sysctl net.inet.tcp.blackhole Ns Op = Ns Brq "0 | 1 | 2"
 .Cd sysctl net.inet.udp.blackhole Ns Op = Ns Brq "0 | 1"
 .Sh DESCRIPTION
 The
 .Nm
 .Xr sysctl 8
 MIB is used to control system behaviour when connection requests
 are received on SCTP, TCP, or UDP ports where there is no socket listening.
 .Pp
 The blackhole behaviour is useful to slow down an attacker who is port-scanning
 a system in an attempt to detect vulnerable services.
 It might also slow down an attempted denial of service attack.
 .Ss SCTP
 Setting the SCTP blackhole MIB to a numeric value of one
 will prevent sending an ABORT packet in response to an incoming INIT.
 A MIB value of two will do the same, but will also prevent sending an ABORT packet
 when unexpected packets are received.
 .Ss TCP
 Normal behaviour, when a TCP SYN segment is received on a port where
 there is no socket accepting connections, is for the system to return
 a RST segment, and drop the connection.
 The connecting system will
 see this as a
 .Dq Connection refused .
 By setting the TCP blackhole
 MIB to a numeric value of one, the incoming SYN segment
 is merely dropped, and no RST is sent, making the system appear
 as a blackhole.
 By setting the MIB value to two, any segment arriving
 on a closed port is dropped without returning a RST.
 This provides some degree of protection against stealth port scans.
 .Ss UDP
 Enabling blackhole behaviour turns off the sending
 of an ICMP port unreachable message in response to a UDP datagram which
 arrives on a port where there is no socket listening.
 It must be noted that this behaviour will prevent remote systems from running
 .Xr traceroute 8
 to a system.
 .Sh WARNING
 The SCTP, TCP, and UDP blackhole features should not be regarded as a replacement
 for firewall solutions.
 Better security would consist of the
 .Nm
 .Xr sysctl 8
 MIB used in conjunction with one of the available firewall packages.
 .Pp
 This mechanism is not a substitute for securing a system.
 It should be used together with other security mechanisms.
 .Sh SEE ALSO
 .Xr ip 4 ,
 .Xr sctp 4 ,
 .Xr tcp 4 ,
 .Xr udp 4 ,
 .Xr ipf 8 ,
 .Xr ipfw 8 ,
 .Xr pfctl 8 ,
 .Xr sysctl 8
 .Sh HISTORY
 The TCP and UDP
 .Nm
 MIBs
 first appeared in
 .Fx 4.0 .
 .Pp
-The SCTP 
-.Nm 
+The SCTP
+.Nm
 MIB first appeared in
 .Fx 9.1 .
 .Sh AUTHORS
 .An Geoffrey M. Rehmet
Index: head/share/man/man4/ioat.4
===================================================================
--- head/share/man/man4/ioat.4	(revision 292204)
+++ head/share/man/man4/ioat.4	(revision 292205)
@@ -1,227 +1,227 @@
 .\" Copyright (c) 2015 EMC / Isilon Storage Division
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .\" $FreeBSD$
 .\"
 .Dd December 9, 2015
 .Dt IOAT 4
 .Os
 .Sh NAME
 .Nm I/OAT
 .Nd Intel I/O Acceleration Technology
 .Sh SYNOPSIS
 To compile this driver into your kernel,
 place the following line in your kernel configuration file:
 .Bd -ragged -offset indent
 .Cd "device ioat"
 .Ed
 .Pp
 Or, to load the driver as a module at boot, place the following line in
 .Xr loader.conf 5 :
 .Bd -literal -offset indent
 ioat_load="YES"
 .Ed
 .Pp
 In
 .Xr loader.conf 5 :
 .Pp
 .Cd hw.ioat.force_legacy_interrupts=0
 .Pp
 In
 .Xr loader.conf 5 or
 .Xr sysctl.conf 5 :
 .Pp
 .Cd hw.ioat.enable_ioat_test=0
 .Cd hw.ioat.debug_level=0
 (only critical errors; maximum of 3)
 .Pp
 .Ft typedef void
 .Fn (*bus_dmaengine_callback_t) "void *arg" "int error"
 .Pp
 .Ft bus_dmaengine_t
 .Fn ioat_get_dmaengine "uint32_t channel_index"
 .Ft void
 .Fn ioat_put_dmaengine "bus_dmaengine_t dmaengine"
 .Ft void
 .Fn ioat_acquire "bus_dmaengine_t dmaengine"
 .Ft void
 .Fn ioat_release "bus_dmaengine_t dmaengine"
 .Ft struct bus_dmadesc *
 .Fo ioat_copy
 .Fa "bus_dmaengine_t dmaengine"
 .Fa "bus_addr_t dst"
 .Fa "bus_addr_t src"
 .Fa "bus_size_t len"
 .Fa "bus_dmaengine_callback_t callback_fn"
 .Fa "void *callback_arg"
 .Fa "uint32_t flags"
 .Fc
 .Ft struct bus_dmadesc *
 .Fo ioat_copy_8k_aligned
 .Fa "bus_dmaengine_t dmaengine"
 .Fa "bus_addr_t dst1"
 .Fa "bus_addr_t dst2"
 .Fa "bus_addr_t src1"
 .Fa "bus_addr_t src2"
 .Fa "bus_dmaengine_callback_t callback_fn"
 .Fa "void *callback_arg"
 .Fa "uint32_t flags"
 .Fc
 .Ft struct bus_dmadesc *
 .Fo ioat_blockfill
 .Fa "bus_dmaengine_t dmaengine"
 .Fa "bus_addr_t dst"
 .Fa "uint64_t fillpattern"
 .Fa "bus_size_t len"
 .Fa "bus_dmaengine_callback_t callback_fn"
 .Fa "void *callback_arg"
 .Fa "uint32_t flags"
 .Fc
 .Ft struct bus_dmadesc *
 .Fo ioat_null
 .Fa "bus_dmaengine_t dmaengine"
 .Fa "bus_dmaengine_callback_t callback_fn"
 .Fa "void *callback_arg"
 .Fa "uint32_t flags"
 .Fc
 .Sh DESCRIPTION
 The
 .Nm
 driver provides a kernel API to a variety of DMA engines on some Intel server
 platforms.
 .Pp
 There is a number of DMA channels per CPU package.
 (Typically 4 or 8.)
 Each may be used independently.
 Operations on a single channel proceed sequentially.
 .Pp
 Blockfill operations can be used to write a 64-bit pattern to memory.
 .Pp
 Copy operations can be used to offload memory copies to the DMA engines.
 .Pp
 Null operations do nothing, but may be used to test the interrupt and callback
 mechanism.
 .Pp
 All operations can optionally trigger an interrupt at completion with the
 .Ar DMA_EN_INT
 flag.
 For example, a user might submit multiple operations to the same channel and
 only enable an interrupt and callback for the last operation.
 .Pp
 All operations are safe to use in a non-blocking context with the
 .Ar DMA_NO_WAIT
 flag.
 (Of course, allocations may fail and operations requested with
 .Ar DMA_NO_WAIT
 may return NULL.)
 .Pp
 All operations, as well as
 .Fn ioat_get_dmaengine ,
 can return NULL in special circumstances.
 For example, if the
 .Nm
 driver is being unloaded, or the administrator has induced a hardware reset, or
 a usage error has resulted in a hardware error state that needs to be recovered
 from.
 .Pp
 It is invalid to attempt to submit new DMA operations in a
 .Fa bus_dmaengine_callback_t
 context.
 .Sh USAGE
 A typical user will lookup the DMA engine object for a given channel with
 .Fn ioat_get_dmaengine .
 When the user wants to offload a copy, they will first
 .Fn ioat_acquire
 the
 .Ar bus_dmaengine_t
 object for exclusive access to enqueue operations on that channel.
 Then, they will submit one or more operations using
 .Fn ioat_blockfill ,
 .Fn ioat_copy ,
 or
 .Fn ioat_null .
 After queuing one or more individual DMA operations, they will
 .Fn ioat_release
 the
 .Ar bus_dmaengine_t
 to drop their exclusive access to the channel.
 The routine they provided for the
 .Fa callback_fn
 argument will be invoked with the provided
 .Fa callback_arg
 when the operation is complete.
 When they are finished with the
 .Ar bus_dmaengine_t ,
 the user should
 .Fn ioat_put_dmaengine .
 .Pp
 Users MUST NOT block between
 .Fn ioat_acquire
 and
 .Fn ioat_release .
 Users SHOULD NOT hold
 .Ar bus_dmaengine_t
 references for a very long time to enable fault recovery and kernel module
 unload.
 .Pp
 For an example of usage, see
 .Pa src/sys/dev/ioat/ioat_test.c .
 .Sh FILES
-.Bl -tag -compat
+.Bl -tag
 .It Pa /dev/ioat_test
 test device for
 .Xr ioatcontrol 8
 .El
 .Sh SEE ALSO
 .Xr ioatcontrol 8
 .Sh HISTORY
 The
 .Nm
 driver first appeared in
 .Fx 11.0 .
 .Sh AUTHORS
 The
 .Nm
 driver was developed by
 .An \&Jim Harris Aq Mt jimharris@FreeBSD.org ,
 .An \&Carl Delsey Aq Mt carl.r.delsey@intel.com ,
 and
 .An \&Conrad Meyer Aq Mt cem@FreeBSD.org .
 This manual page was written by
 .An \&Conrad Meyer Aq Mt cem@FreeBSD.org .
 .Sh CAVEATS
 Copy operation takes bus addresses as parameters, not virtual addresses.
 .Pp
 Buffers for individual copy operations must be physically contiguous.
 .Pp
 Copies larger than max transfer size (1MB, but may vary by hardware) are not
 supported.
 Future versions will likely support this by breaking up the transfer into
 smaller sizes.
 .Sh BUGS
 The
 .Nm
 driver only supports blockfill, copy, and null operations at this time.
 The driver does not yet support advanced DMA modes, such as XOR, that some
 I/OAT devices support.
Index: head/share/man/man4/mlx5en.4
===================================================================
--- head/share/man/man4/mlx5en.4	(revision 292204)
+++ head/share/man/man4/mlx5en.4	(revision 292205)
@@ -1,130 +1,130 @@
 .\" Copyright (c) 2015 Mellanox Technologies
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY AUTHOR AND CONTRIBUTORS `AS IS' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL AUTHOR OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .\" $FreeBSD$
 .\"
 .Dd December 3, 2015
-.Dt mlx5en 4
+.Dt MLX5EN 4
 .Os
 .Sh NAME
 .Nm mlx5en
 .Nd "Mellanox ConnectX-4 and ConnectX-4 LX based 100Gb, 50Gb, 40Gb, 25Gb and 10Gb Ethernet adapter driver"
 .Sh SYNOPSIS
 To compile this driver into the kernel,
 place the following lines in your
 kernel configuration file:
 .Bd -ragged -offset indent
 .Cd "options COMPAT_LINUXKPI"
 .Cd "device mlx5"
 .Cd "device mlx5en"
 .Ed
 .Pp
 To load the driver as a module at run-time,
 run the following command as root:
 .Bd -literal -offset indent
 kldload mlx5en
 .Ed
 .Pp
 To load the driver as a
 module at boot time, place the following lines in
 .Xr loader.conf 5 :
 .Bd -literal -offset indent
 mlx5en_load="YES"
 .Ed
 .Sh DESCRIPTION
 The
 .Nm
 driver provides support for PCI Express Ethernet adapters based on
 ConnectX-4 and ConnectX-4 LX.
 The driver supports Jumbo Frames, Transmit/Receive checksum offload,
 TCP segmentation offload (TSO), Large Receive Offload (LRO),
 HW Large Receive Offload (HW LRO), VLAN tag insertion/extraction,
 VLAN checksum offload, VLAN TSO, and Receive Side Steering (RSS).
 .br
 The network interface is named mce.
 .br
 For further hardware information and questions related to hardware
 requirements, see
 .Pa http://www.mellanox.com/ .
 .Pp
 For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh HARDWARE
 The
 .Nm
 driver supports 100Gb, 50Gb, 40Gb, 25Gb and 10Gb Ethernet adapters.
 ConnectX-4 supports:10/20/25/40/50/56/100Gb/s speeds.
 ConnectX-4 LX supports:10/25/40/50Gb/s speeds (and reduced power consumption) :
 .Pp
 .Bl -bullet -compact
 .It
 Mellanox MCX455A-ECAT
 .It
 Mellanox MCX456A-ECAT
 .It
 Mellanox MCX415A-CCAT
 .It
 Mellanox MCX416A-CCAT
 .It
 Mellanox MCX455A-FCAT
 .It
 Mellanox MCX456A-FCAT
 .It
 Mellanox MCX415A-BCAT
 .It
 Mellanox MCX416A-BCAT
 .It
 Mellanox MCX4131A-GCAT
 .It
 Mellanox MCX4131A-BCAT
 .It
 Mellanox MCX4121A-ACAT
 .It
 Mellanox MCX4111A-ACAT
 .It
 Mellanox MCX4121A-XCAT
 .It
 Mellanox MCX4111A-XCAT
 .El
 .Sh SUPPORT
 For general information and support,
 go to the Mellanox support website at:
 .Pa http://www.mellanox.com/ .
 .Pp
 If an issue is identified with this driver with a supported adapter,
 email all the specific information related to the issue to
 .Aq Mt freebsd-drivers@mellanox.com .
 .Sh SEE ALSO
 .Xr ifconfig 8
 .Sh HISTORY
 The
 .Nm
 device driver first appeared in
 .Fx 11.0 .
 .Sh AUTHORS
 .An -nosplit
 The
 .Nm
 driver was written by
 .An Mellanox Technologies <freebsd-drivers@mellanox.com> .
Index: head/share/man/man4/pass.4
===================================================================
--- head/share/man/man4/pass.4	(revision 292204)
+++ head/share/man/man4/pass.4	(revision 292205)
@@ -1,232 +1,232 @@
 .\"
 .\" Copyright (c) 1998, 1999 Kenneth D. Merry.
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 3. The name of the author may not be used to endorse or promote products
 .\"    derived from this software without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .\" $FreeBSD$
 .\"
 .Dd March 17, 2015
 .Dt PASS 4
 .Os
 .Sh NAME
 .Nm pass
 .Nd CAM application passthrough driver
 .Sh SYNOPSIS
 .Cd device pass
 .Sh DESCRIPTION
 The
 .Nm
 driver provides a way for userland applications to issue CAM CCBs to the
 kernel.
 .Pp
 Since the
 .Nm
 driver allows direct access to the CAM subsystem, system administrators
 should exercise caution when granting access to this driver.
 If used
 improperly, this driver can allow userland applications to crash a machine
 or cause data loss.
 .Pp
 The
 .Nm
 driver attaches to every
 .Tn SCSI
 and
 .Tn ATA
 device found in the system.
 Since it attaches to every device, it provides a generic means of accessing
 .Tn SCSI
 and
 .Tn ATA
 devices, and allows the user to access devices which have no
 "standard" peripheral driver associated with them.
 .Sh KERNEL CONFIGURATION
 It is only necessary to configure one
 .Nm
 device in the kernel;
 .Nm
 devices are automatically allocated as
 .Tn SCSI
 and
 .Tn ATA
 devices are found.
 .Sh IOCTLS
 .Bl -tag -width 5n
 .It CAMIOCOMMAND union ccb *
 This ioctl takes most kinds of CAM CCBs and passes them through to the CAM
 transport layer for action.
 Note that some CCB types are not allowed
 through the passthrough device, and must be sent through the
 .Xr xpt 4
 device instead.
 Some examples of xpt-only CCBs are XPT_SCAN_BUS,
 XPT_DEV_MATCH, XPT_RESET_BUS, XPT_SCAN_LUN, XPT_ENG_INQ, and XPT_ENG_EXEC.
 These CCB types have various attributes that make it illogical or
 impossible to service them through the passthrough interface.
 .It CAMGETPASSTHRU union ccb *
 This ioctl takes an XPT_GDEVLIST CCB, and returns the passthrough device
 corresponding to the device in question.
 Although this ioctl is available through the
 .Nm
 driver, it is of limited use, since the caller must already know that
 the device in question is a passthrough device if they are issuing this
 ioctl.
 It is probably more useful to issue this ioctl through the
 .Xr xpt 4
 device.
 .It CAMIOQUEUE union ccb *
 Queue a CCB to the
 .Xr pass 4
 driver to be executed asynchronously.
 The caller may use
 .Xr select 2 ,
-.Xr poll 2 
+.Xr poll 2
 or
 .Xr kevent 2
 to receive notification when the CCB has completed.
 .Pp
 This ioctl takes most CAM CCBs, but some CCB types are not allowed through
 the pass device, and must be sent through the
 .Xr xpt 4
 device instead.
 Some examples of xpt-only CCBs are XPT_SCAN_BUS,
 XPT_DEV_MATCH, XPT_RESET_BUS, XPT_SCAN_LUN, XPT_ENG_INQ, and XPT_ENG_EXEC.
 These CCB types have various attributes that make it illogical or
 impossible to service them through the passthrough interface.
 .Pp
 Although the
 .Dv CAMIOQUEUE
 ioctl is not defined to take an argument, it does require a
 pointer to a union ccb.
-It is not defined to take an argument to avoid an extra malloc and copy 
-inside the generic 
+It is not defined to take an argument to avoid an extra malloc and copy
+inside the generic
 .Xr ioctl 2
 handler.
-.pp
+.Pp
 The completed CCB will be returned via the
 .Dv CAMIOGET
 ioctl.
 An error will only be returned from the
 .Dv CAMIOQUEUE
 ioctl if there is an error allocating memory for the request or copying
 memory from userland.
 All other errors will be reported as standard CAM CCB status errors.
 Since the CCB is not copied back to the user process from the pass driver
 in the
 .Dv CAMIOQUEUE
 ioctl, the user's passed-in CCB will not be modfied.
 This is the case even with immediate CCBs.
 Instead, the completed CCB must be retrieved via the
 .Dv CAMIOGET
 ioctl and the status examined.
 .Pp
 Multiple CCBs may be queued via the
 .Dv CAMIOQUEUE
 ioctl at any given time, and they may complete in a different order than
 the order that they were submitted.
 The caller must take steps to identify CCBs that are queued and completed.
 The
 .Dv periph_priv
 structure inside struct ccb_hdr is available for userland use with the
 .Dv CAMIOQUEUE
 and
 .Dv CAMIOGET
 ioctls, and will be preserved across calls.
 Also, the periph_links linked list pointers inside struct ccb_hdr are
 available for userland use with the
 .Dv CAMIOQUEUE
 and
 .Dv CAMIOGET
 ioctls and will be preserved across calls.
 .It CAMIOGET union ccb *
 Retrieve completed CAM CCBs queued via the
 .Dv CAMIOQUEUE
 ioctl.
 An error will only be returned from the
 .Dv CAMIOGET
 ioctl if the
 .Xr pass 4
 driver fails to copy data to the user process or if there are no completed
 CCBs available to retrieve.
 If no CCBs are available to retrieve,
-errno will be set to 
+errno will be set to
 .Dv ENOENT .
 .Pp
 All other errors will be reported as standard CAM CCB status errors.
 .Pp
 Although the
 .Dv CAMIOGET
 ioctl is not defined to take an argument, it does require a
 pointer to a union ccb.
-It is not defined to take an argument to avoid an extra malloc and copy 
-inside the generic 
+It is not defined to take an argument to avoid an extra malloc and copy
+inside the generic
 .Xr ioctl 2
 handler.
 .Pp
 The pass driver will report via
 .Xr select 2 ,
-.Xr poll 2 
+.Xr poll 2
 or
 .Xr kevent 2
 when a CCB has completed.
 One CCB may be retrieved per
 .Dv CAMIOGET
 call.
 CCBs may be returned in an order different than the order they were
 submitted.
 So the caller should use the
 .Dv periph_priv
 area inside the CCB header to store pointers to identifying information.
 .El
 .Sh FILES
 .Bl -tag -width /dev/passn -compact
 .It Pa /dev/pass Ns Ar n
 Character device nodes for the
 .Nm
 driver.
 There should be one of these for each device accessed through the
 CAM subsystem.
 .El
 .Sh DIAGNOSTICS
 None.
 .Sh SEE ALSO
 .Xr kqueue 2 ,
 .Xr poll 2 ,
 .Xr select 2 ,
 .Xr cam 3 ,
 .Xr cam_cdbparse 3 ,
 .Xr cam 4 ,
 .Xr cd 4 ,
 .Xr ctl 4 ,
 .Xr da 4 ,
 .Xr sa 4 ,
 .Xr xpt 4 ,
 .Xr camcontrol 8 ,
 .Xr camdd 8
 .Sh HISTORY
 The CAM passthrough driver first appeared in
 .Fx 3.0 .
 .Sh AUTHORS
 .An Kenneth Merry Aq Mt ken@FreeBSD.org