Deleted Added
full compact
devstat.9 (84306) devstat.9 (89124)
1.\"
2.\" Copyright (c) 1998, 1999 Kenneth D. Merry.
3.\" All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright

--- 11 unchanged lines hidden (view full) ---

20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
1.\"
2.\" Copyright (c) 1998, 1999 Kenneth D. Merry.
3.\" All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright

--- 11 unchanged lines hidden (view full) ---

20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\" $FreeBSD: head/share/man/man9/devstat.9 84306 2001-10-01 16:09:29Z ru $
28.\" $FreeBSD: head/share/man/man9/devstat.9 89124 2002-01-09 11:43:48Z mpp $
29.\"
30.Dd May 22, 1998
31.Dt DEVSTAT 9
32.Os
33.Sh NAME
34.Nm devstat ,
35.Nm devstat_add_entry ,
36.Nm devstat_end_transaction ,

--- 61 unchanged lines hidden (view full) ---

98.Nm
99list, it should be set to 0.
100.It flags
101Flags indicating operations supported or not supported by the device. See
102below for details.
103.It device_type
104The device type. This is broken into three sections: base device type
105(e.g. direct access, CDROM, sequential access), interface type (IDE, SCSI
29.\"
30.Dd May 22, 1998
31.Dt DEVSTAT 9
32.Os
33.Sh NAME
34.Nm devstat ,
35.Nm devstat_add_entry ,
36.Nm devstat_end_transaction ,

--- 61 unchanged lines hidden (view full) ---

98.Nm
99list, it should be set to 0.
100.It flags
101Flags indicating operations supported or not supported by the device. See
102below for details.
103.It device_type
104The device type. This is broken into three sections: base device type
105(e.g. direct access, CDROM, sequential access), interface type (IDE, SCSI
106or other) and a passthrough flag to indicate pasthrough devices. See below
106or other) and a pass-through flag to indicate pas-through devices. See below
107for a complete list of types.
108.It priority
109The device priority. The priority is used to determine how devices are
110sorted within
111.Nm devstat Ns 's
112list of devices. Devices are sorted first by priority (highest to lowest),
113and then by attach order. See below for a complete list of available
114priorities.

--- 126 unchanged lines hidden (view full) ---

241to calculate the device busy time.
242.It flags
243These flags indicate which statistics measurements are supported by a
244particular device. These flags are primarily intended to serve as an aid
245to userland programs that decipher the statistics.
246.It device_type
247This is the device type. It consists of three parts: the device type
248(e.g. direct access, CDROM, sequential access, etc.), the interface (IDE,
107for a complete list of types.
108.It priority
109The device priority. The priority is used to determine how devices are
110sorted within
111.Nm devstat Ns 's
112list of devices. Devices are sorted first by priority (highest to lowest),
113and then by attach order. See below for a complete list of available
114priorities.

--- 126 unchanged lines hidden (view full) ---

241to calculate the device busy time.
242.It flags
243These flags indicate which statistics measurements are supported by a
244particular device. These flags are primarily intended to serve as an aid
245to userland programs that decipher the statistics.
246.It device_type
247This is the device type. It consists of three parts: the device type
248(e.g. direct access, CDROM, sequential access, etc.), the interface (IDE,
249SCSI or other) and whether or not the device in question is a passthrough
249SCSI or other) and whether or not the device in question is a pass-through
250driver. See below for a complete list of device types.
251.It priority
252This is the priority. This is the first parameter used to determine where
253to insert a device in the
254.Nm
255list. The second parameter is attach order. See below for a list of
256available priorities.
257.El
258.Pp
250driver. See below for a complete list of device types.
251.It priority
252This is the priority. This is the first parameter used to determine where
253to insert a device in the
254.Nm
255list. The second parameter is attach order. See below for a list of
256available priorities.
257.El
258.Pp
259Each device is given a device type. Passthrough devices have the same
259Each device is given a device type. Pass-through devices have the same
260underlying device type and interface as the device they provide an
260underlying device type and interface as the device they provide an
261interface for, but they also have the passthrough flag set. The base
261interface for, but they also have the pass-through flag set. The base
262device types are identical to the
263.Tn SCSI
264device type numbers, so with
265.Tn SCSI
266peripherals, the device type returned from an inquiry is usually ORed with
267the
268.Tn SCSI
262device types are identical to the
263.Tn SCSI
264device type numbers, so with
265.Tn SCSI
266peripherals, the device type returned from an inquiry is usually ORed with
267the
268.Tn SCSI
269interface type and the passthrough flag if appropriate. The device type
269interface type and the pass-through flag if appropriate. The device type
270flags are as follows:
271.Bd -literal -offset indent
272typedef enum {
273 DEVSTAT_TYPE_DIRECT = 0x000,
274 DEVSTAT_TYPE_SEQUENTIAL = 0x001,
275 DEVSTAT_TYPE_PRINTER = 0x002,
276 DEVSTAT_TYPE_PROCESSOR = 0x003,
277 DEVSTAT_TYPE_WORM = 0x004,

--- 138 unchanged lines hidden ---
270flags are as follows:
271.Bd -literal -offset indent
272typedef enum {
273 DEVSTAT_TYPE_DIRECT = 0x000,
274 DEVSTAT_TYPE_SEQUENTIAL = 0x001,
275 DEVSTAT_TYPE_PRINTER = 0x002,
276 DEVSTAT_TYPE_PROCESSOR = 0x003,
277 DEVSTAT_TYPE_WORM = 0x004,

--- 138 unchanged lines hidden ---