csio_build csio_build_visit csio_decode csio_decode_visit buff_decode buff_decode_visit csio_encode csio_encode_visit buff_encode_visit - CAM user library SCSI buffer parsing routines
Lb libcam
These functions may be used in new applications, but users may find it
easier to use the various SCSI CCB building functions included with the
cam(3)
library.
(e.g.
cam_fill_csio (,);
scsi_start_stop (,);
and
scsi_read_write ());
csio_build ();
builds up a
ccb_scsiio
structure based on the information provided in
the variable argument list.
It gracefully handles a NULL
Fa data_ptr
argument passed to it.
Fa dxfer_len is the length of the data phase; the data transfer direction is determined by the Fa flags argument.
Fa data_ptr is the data buffer used during the SCSI data phase. If no data is to be transferred for the SCSI command in question, this should be set to NULL. If there is data to transfer for the command, this buffer must be at least Fa dxfer_len long.
Fa flags are the flags defined in In cam/cam_ccb.h :
/* Common CCB header */ /* CAM CCB flags */ typedef enum { CAM_CDB_POINTER = 0x00000001,/* The CDB field is a pointer */ CAM_QUEUE_ENABLE = 0x00000002,/* SIM queue actions are enabled */ CAM_CDB_LINKED = 0x00000004,/* CCB contains a linked CDB */ CAM_SCATTER_VALID = 0x00000010,/* Scatter/gather list is valid */ CAM_DIS_AUTOSENSE = 0x00000020,/* Disable autosense feature */ CAM_DIR_RESV = 0x00000000,/* Data direction (00:reserved) */ CAM_DIR_IN = 0x00000040,/* Data direction (01:DATA IN) */ CAM_DIR_OUT = 0x00000080,/* Data direction (10:DATA OUT) */ CAM_DIR_NONE = 0x000000C0,/* Data direction (11:no data) */ CAM_DIR_MASK = 0x000000C0,/* Data direction Mask */ CAM_SOFT_RST_OP = 0x00000100,/* Use Soft reset alternative */ CAM_ENG_SYNC = 0x00000200,/* Flush resid bytes on complete */ CAM_DEV_QFRZDIS = 0x00000400,/* Disable DEV Q freezing */ CAM_DEV_QFREEZE = 0x00000800,/* Freeze DEV Q on execution */ CAM_HIGH_POWER = 0x00001000,/* Command takes a lot of power */ CAM_SENSE_PTR = 0x00002000,/* Sense data is a pointer */ CAM_SENSE_PHYS = 0x00004000,/* Sense pointer is physical addr*/ CAM_TAG_ACTION_VALID = 0x00008000,/* Use the tag action in this ccb*/ CAM_PASS_ERR_RECOVER = 0x00010000,/* Pass driver does err. recovery*/ CAM_DIS_DISCONNECT = 0x00020000,/* Disable disconnect */ CAM_SG_LIST_PHYS = 0x00040000,/* SG list has physical addrs. */ CAM_MSG_BUF_PHYS = 0x00080000,/* Message buffer ptr is physical*/ CAM_SNS_BUF_PHYS = 0x00100000,/* Autosense data ptr is physical*/ CAM_DATA_PHYS = 0x00200000,/* SG/Buffer data ptrs are phys. */ CAM_CDB_PHYS = 0x00400000,/* CDB pointer is physical */ CAM_ENG_SGLIST = 0x00800000,/* SG list is for the HBA engine */ /* Phase cognizant mode flags */ CAM_DIS_AUTOSRP = 0x01000000,/* Disable autosave/restore ptrs */ CAM_DIS_AUTODISC = 0x02000000,/* Disable auto disconnect */ CAM_TGT_CCB_AVAIL = 0x04000000,/* Target CCB available */ CAM_TGT_PHASE_MODE = 0x08000000,/* The SIM runs in phase mode */ CAM_MSGB_VALID = 0x20000000,/* Message buffer valid */ CAM_STATUS_VALID = 0x40000000,/* Status buffer valid */ CAM_DATAB_VALID = 0x80000000,/* Data buffer valid */ /* Host target Mode flags */ CAM_TERM_IO = 0x20000000,/* Terminate I/O Message sup. */ CAM_DISCONNECT = 0x40000000,/* Disconnects are mandatory */ CAM_SEND_STATUS = 0x80000000,/* Send status after data phase */ } ccb_flags;
Multiple flags should be ORed together. Any of the CCB flags may be used, although it is worth noting several important ones here:
The Fa retry_count tells the kernel how many times to retry the command in question. The retry count is ignored unless the pass(4) driver is told to enable error recovery via the CAM_PASS_ERR_RECOVER flag.
The Fa timeout tells the kernel how long to wait for the given command to complete. If the timeout expires and the command has not completed, the CCB will be returned from the kernel with an appropriate error status.
Fa cmd_spec is a CDB format specifier used to build up the SCSI CDB. This text string is made up of a list of field specifiers. Field specifiers specify the value for each CDB field (including indicating that the value be taken from the next argument in the variable argument list), the width of the field in bits or bytes, and an optional name. White space is ignored, and the pound sign ('#') introduces a comment that ends at the end of the current line.
The optional name is the first part of a field specifier and is in curly braces. The text in curly braces in this example are the names:
"{PS} v:b1 {Reserved} 0:b1 {Page Code} v:b6 # Mode select page"
This field specifier has two one bit fields and one six bit field. The second one bit field is the constant value 0 and the first one bit field and the six bit field are taken from the variable argument list. Multi byte fields are swapped into the SCSI byte order in the CDB and white space is ignored.
When the field is a hex value or the letter v, (e.g., Fa 1A or Fa v ) then a single byte value is copied to the next unused byte of the CDB. When the letter Fa v is used the next integer argument is taken from the variable argument list and that value used.
A constant hex value followed by a field width specifier or the letter Fa v followed by a field width specifier (e.g., Fa 3:4 , Fa 3:b4 , Fa 3:i3 , Fa v:i3 ) specifies a field of a given bit or byte width. Either the constant value or (for the V specifier) the next integer value from the variable argument list is copied to the next unused bits or bytes of the CDB.
A decimal number or the letter Fa b followed by a decimal number field width indicates a bit field of that width. The bit fields are packed as tightly as possible beginning with the high bit (so that it reads the same as the SCSI spec), and a new byte of the CDB is started whenever a byte fills completely or when an Fa i field is encountered.
A field width specifier consisting of the letter Fa i followed by either 1, 2, 3 or 4 indicates a 1, 2, 3 or 4 byte integral value that must be swapped into SCSI byte order (MSB first).
For the Fa v field specifier the next integer argument is taken from the variable argument list and that value is used swapped into SCSI byte order.
csio_build_visit ();
operates similarly to
csio_build (,);
except that the values to substitute for variable arguments in
Fa cmd_spec
are retrieved via the
arg_get ();
function passed in to
csio_build_visit ();
instead of via
stdarg(3).
The
arg_get ();
function takes two arguments:
csio_decode ();
is used to decode information from the data in phase of the SCSI
transfer.
The decoding is similar to
the command specifier processing of
csio_build ();
except that the data is extracted from the data pointed to by
Fa csio->data_ptr .
The stdarg list should be pointers to integers instead of integer
values.
A seek field type and a suppression modifier are added.
The
Fa *
suppression modifier (e.g.,
Fa *i3
or
Fa *b4 )
suppresses assignment from the field and can be used to skip
over bytes or bits in the data, without having to copy
them to a dummy variable in the arg list.
The seek field type Fa s permits you to skip over data. This seeks to an absolute position (Fa s3 ) or a relative position (Fa s+3 ) in the data, based on whether or not the presence of the '+' sign. The seek value can be specified as Fa v and the next integer value from the argument list will be used as the seek value.
csio_decode_visit ();
operates like
csio_decode ();
except that instead of placing the decoded contents of the buffer in
variadic arguments, the decoded buffer contents are returned to the user
via the
arg_put ();
function that is passed in.
The
arg_put ();
function takes several arguments:
buff_decode ();
decodes an arbitrary data buffer using the method
described above for
csio_decode (.);
buff_decode_visit ();
decodes an arbitrary data buffer using the method described above for
csio_decode_visit (.);
csio_encode ();
encodes the
Fa data_ptr
portion (not the CDB!) of a
ccb_scsiio
structure, using the method described above for
csio_build (.);
csio_encode_visit ();
encodes the
Fa data_ptr
portion (not the CDB!) of a
ccb_scsiio
structure, using the method described above for
csio_build_visit (.);
buff_encode_visit ();
encodes an arbitrary data pointer, using the method described
above for
csio_build_visit (.);
csio_decode (,);
csio_decode_visit (,);
buff_decode (,);
and
buff_decode_visit ();
return the number of assignments performed.
Many systems have comparable interfaces to permit a user to construct a SCSI command in user space.
The old scsireq data structure was almost identical to the SGI /dev/scsi data structure. If anyone knows the name of the authors it should go here; Peter Dufault first read about it in a 1989 Sun Expert magazine.
The new CCB data structures are derived from the CAM-2 and CAM-3 specifications.
An Peter Dufault implemented a clone of SGI's interface in BSD 386 that led to the original Fx SCSI library and the related kernel ioctl. If anyone needs that for compatibility contact [email protected].
Some of the CCB flag descriptions really do not belong here. Rather they belong in a generic CCB man page. Since that man page has not yet been written, the shorter descriptions here will have to suffice.
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |