28c28
< .\" $FreeBSD: head/share/man/man9/devstat.9 119964 2003-09-10 19:24:35Z ru $
---
> .\" $FreeBSD: head/share/man/man9/devstat.9 121380 2003-10-23 01:54:06Z hmp $
71c71,72
< statistics, as its name implies. The idea is to keep reasonably detailed
---
> statistics, as its name implies.
> The idea is to keep reasonably detailed
81c82,83
< subsystem. The caller is expected to have already allocated \fBand zeroed\fR
---
> subsystem.
> The caller is expected to have already allocated \fBand zeroed\fR
95c97,98
< Block size of the device, if supported. If the device does not support a
---
> Block size of the device, if supported.
> If the device does not support a
101,102c104,105
< Flags indicating operations supported or not supported by the device. See
< below for details.
---
> Flags indicating operations supported or not supported by the device.
> See below for details.
104c107,108
< The device type. This is broken into three sections: base device type
---
> The device type.
> This is broken into three sections: base device type
106,107c110,111
< or other) and a pass-through flag to indicate pas-through devices. See below
< for a complete list of types.
---
> or other) and a pass-through flag to indicate pas-through devices.
> See below for a complete list of types.
109c113,114
< The device priority. The priority is used to determine how devices are
---
> The device priority.
> The priority is used to determine how devices are
112,113c117,120
< list of devices. Devices are sorted first by priority (highest to lowest),
< and then by attach order. See below for a complete list of available
---
> list of devices.
> Devices are sorted first by priority (highest to lowest),
> and then by attach order.
> See below for a complete list of available
120,121c127,130
< subsystem. It takes the devstat structure for the device in question as
< an argument. The
---
> subsystem.
> It takes the devstat structure for the device in question as
> an argument.
> The
128c137,138
< subsystem. The busy count is incremented with each transaction start.
---
> subsystem.
> The busy count is incremented with each transaction start.
138c148,149
< subsystem. It takes four arguments:
---
> subsystem.
> It takes four arguments:
147c158,159
< Transaction tag type. See below for tag types.
---
> Transaction tag type.
> See below for tag types.
167c179,180
< structure is placed in a linked list when it is registered. The
---
> structure is placed in a linked list when it is registered.
> The
173,174c186,189
< The device number is a unique identifier for each device. The device
< number is incremented for each new device that is registered. The device
---
> The device number is a unique identifier for each device.
> The device
> number is incremented for each new device that is registered.
> The device
179c194,195
< identify itself. (e.g.\&
---
> identify itself.
> (e.g.\&
188,189c204,206
< This is the number of bytes that have been written to the device. This
< number is currently an unsigned 64 bit integer. This will hopefully
---
> This is the number of bytes that have been written to the device.
> This number is currently an unsigned 64 bit integer.
> This will hopefully
204c221,222
< writes. For instance,
---
> writes.
> For instance,
208,209c226,228
< devices. The test unit ready command does not read or write any data. It
< merely causes the device to return its status.
---
> devices.
> The test unit ready command does not read or write any data.
> It merely causes the device to return its status.
218c237,238
< are being called in client code. There should be one and only one
---
> are being called in client code.
> There should be one and only one
224c244,245
< are sent to a device. See below for a list of tag types.
---
> are sent to a device.
> See below for a list of tag types.
231c252,253
< zero. This is only updated when the busy count returns to zero.
---
> zero.
> This is only updated when the busy count returns to zero.
239c261,262
< that a transaction last completed. It is used along with
---
> that a transaction last completed.
> It is used along with
244c267,268
< particular device. These flags are primarily intended to serve as an aid
---
> particular device.
> These flags are primarily intended to serve as an aid
247c271,272
< This is the device type. It consists of three parts: the device type
---
> This is the device type.
> It consists of three parts: the device type
250c275,276
< driver. See below for a complete list of device types.
---
> driver.
> See below for a complete list of device types.
252c278,279
< This is the priority. This is the first parameter used to determine where
---
> This is the priority.
> This is the first parameter used to determine where
255c282,284
< list. The second parameter is attach order. See below for a list of
---
> list.
> The second parameter is attach order.
> See below for a list of
259c288,289
< Each device is given a device type. Pass-through devices have the same
---
> Each device is given a device type.
> Pass-through devices have the same
261c291,292
< interface for, but they also have the pass-through flag set. The base
---
> interface for, but they also have the pass-through flag set.
> The base
269c300,301
< interface type and the pass-through flag if appropriate. The device type
---
> interface type and the pass-through flag if appropriate.
> The device type
300c332,333
< list. The priorities are as follows:
---
> list.
> The priorities are as follows:
317c350,351
< supported or not supported. The
---
> supported or not supported.
> The
328c362,363
< This device supports a blocksize, but it is currently unavailable. This
---
> This device supports a blocksize, but it is currently unavailable.
> This
364c399,400
< tag definitions. In CAM, for instance, the
---
> tag definitions.
> In CAM, for instance, the
378c414,415
< statistics. Userland programs use this version, via the
---
> statistics.
> Userland programs use this version, via the
410c447,448
< architecture to accurately measure time per transaction. The only feasible
---
> architecture to accurately measure time per transaction.
> The only feasible
412c450,451
< timestamp for every transaction. This measurement is probably not
---
> timestamp for every transaction.
> This measurement is probably not
< .\" $FreeBSD: head/share/man/man9/devstat.9 119964 2003-09-10 19:24:35Z ru $
---
> .\" $FreeBSD: head/share/man/man9/devstat.9 121380 2003-10-23 01:54:06Z hmp $
71c71,72
< statistics, as its name implies. The idea is to keep reasonably detailed
---
> statistics, as its name implies.
> The idea is to keep reasonably detailed
81c82,83
< subsystem. The caller is expected to have already allocated \fBand zeroed\fR
---
> subsystem.
> The caller is expected to have already allocated \fBand zeroed\fR
95c97,98
< Block size of the device, if supported. If the device does not support a
---
> Block size of the device, if supported.
> If the device does not support a
101,102c104,105
< Flags indicating operations supported or not supported by the device. See
< below for details.
---
> Flags indicating operations supported or not supported by the device.
> See below for details.
104c107,108
< The device type. This is broken into three sections: base device type
---
> The device type.
> This is broken into three sections: base device type
106,107c110,111
< or other) and a pass-through flag to indicate pas-through devices. See below
< for a complete list of types.
---
> or other) and a pass-through flag to indicate pas-through devices.
> See below for a complete list of types.
109c113,114
< The device priority. The priority is used to determine how devices are
---
> The device priority.
> The priority is used to determine how devices are
112,113c117,120
< list of devices. Devices are sorted first by priority (highest to lowest),
< and then by attach order. See below for a complete list of available
---
> list of devices.
> Devices are sorted first by priority (highest to lowest),
> and then by attach order.
> See below for a complete list of available
120,121c127,130
< subsystem. It takes the devstat structure for the device in question as
< an argument. The
---
> subsystem.
> It takes the devstat structure for the device in question as
> an argument.
> The
128c137,138
< subsystem. The busy count is incremented with each transaction start.
---
> subsystem.
> The busy count is incremented with each transaction start.
138c148,149
< subsystem. It takes four arguments:
---
> subsystem.
> It takes four arguments:
147c158,159
< Transaction tag type. See below for tag types.
---
> Transaction tag type.
> See below for tag types.
167c179,180
< structure is placed in a linked list when it is registered. The
---
> structure is placed in a linked list when it is registered.
> The
173,174c186,189
< The device number is a unique identifier for each device. The device
< number is incremented for each new device that is registered. The device
---
> The device number is a unique identifier for each device.
> The device
> number is incremented for each new device that is registered.
> The device
179c194,195
< identify itself. (e.g.\&
---
> identify itself.
> (e.g.\&
188,189c204,206
< This is the number of bytes that have been written to the device. This
< number is currently an unsigned 64 bit integer. This will hopefully
---
> This is the number of bytes that have been written to the device.
> This number is currently an unsigned 64 bit integer.
> This will hopefully
204c221,222
< writes. For instance,
---
> writes.
> For instance,
208,209c226,228
< devices. The test unit ready command does not read or write any data. It
< merely causes the device to return its status.
---
> devices.
> The test unit ready command does not read or write any data.
> It merely causes the device to return its status.
218c237,238
< are being called in client code. There should be one and only one
---
> are being called in client code.
> There should be one and only one
224c244,245
< are sent to a device. See below for a list of tag types.
---
> are sent to a device.
> See below for a list of tag types.
231c252,253
< zero. This is only updated when the busy count returns to zero.
---
> zero.
> This is only updated when the busy count returns to zero.
239c261,262
< that a transaction last completed. It is used along with
---
> that a transaction last completed.
> It is used along with
244c267,268
< particular device. These flags are primarily intended to serve as an aid
---
> particular device.
> These flags are primarily intended to serve as an aid
247c271,272
< This is the device type. It consists of three parts: the device type
---
> This is the device type.
> It consists of three parts: the device type
250c275,276
< driver. See below for a complete list of device types.
---
> driver.
> See below for a complete list of device types.
252c278,279
< This is the priority. This is the first parameter used to determine where
---
> This is the priority.
> This is the first parameter used to determine where
255c282,284
< list. The second parameter is attach order. See below for a list of
---
> list.
> The second parameter is attach order.
> See below for a list of
259c288,289
< Each device is given a device type. Pass-through devices have the same
---
> Each device is given a device type.
> Pass-through devices have the same
261c291,292
< interface for, but they also have the pass-through flag set. The base
---
> interface for, but they also have the pass-through flag set.
> The base
269c300,301
< interface type and the pass-through flag if appropriate. The device type
---
> interface type and the pass-through flag if appropriate.
> The device type
300c332,333
< list. The priorities are as follows:
---
> list.
> The priorities are as follows:
317c350,351
< supported or not supported. The
---
> supported or not supported.
> The
328c362,363
< This device supports a blocksize, but it is currently unavailable. This
---
> This device supports a blocksize, but it is currently unavailable.
> This
364c399,400
< tag definitions. In CAM, for instance, the
---
> tag definitions.
> In CAM, for instance, the
378c414,415
< statistics. Userland programs use this version, via the
---
> statistics.
> Userland programs use this version, via the
410c447,448
< architecture to accurately measure time per transaction. The only feasible
---
> architecture to accurately measure time per transaction.
> The only feasible
412c450,451
< timestamp for every transaction. This measurement is probably not
---
> timestamp for every transaction.
> This measurement is probably not