aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/isci/core/scic_io_request.h
diff options
context:
space:
mode:
authorDan Williams <dan.j.williams@intel.com>2011-05-08 11:47:15 -0700
committerDan Williams <dan.j.williams@intel.com>2011-07-03 04:04:47 -0700
commit67ea838d17acdad3331aeae848683c768df96aaa (patch)
tree30a80c95a1add14babf985a108973cc9c3caac83 /drivers/scsi/isci/core/scic_io_request.h
parentisci: make command/response iu explicit request object members (diff)
downloadlinux-dev-67ea838d17acdad3331aeae848683c768df96aaa.tar.xz
linux-dev-67ea838d17acdad3331aeae848683c768df96aaa.zip
isci: unify request data structures
Make scic_sds_request a proper member of isci_request. Also let's us get rid of the dma pool object size tracking since we now know that all requests are sizeof(isci_request). While cleaning up the construct routine incidentally replaced SCI_FIELD_OFFSET with offsetof. Reported-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/scsi/isci/core/scic_io_request.h')
-rw-r--r--drivers/scsi/isci/core/scic_io_request.h33
1 files changed, 1 insertions, 32 deletions
diff --git a/drivers/scsi/isci/core/scic_io_request.h b/drivers/scsi/isci/core/scic_io_request.h
index cb3667decb3c..f7c6d426f8c0 100644
--- a/drivers/scsi/isci/core/scic_io_request.h
+++ b/drivers/scsi/isci/core/scic_io_request.h
@@ -102,41 +102,10 @@ typedef enum {
} SCIC_TRANSPORT_PROTOCOL;
-
-/**
- * scic_io_request_construct() - This method is called by the SCI user to
- * construct all SCI Core IO requests. Memory initialization and
- * functionality common to all IO request types is performed in this method.
- * @scic_controller: the handle to the core controller object for which to
- * build an IO request.
- * @scic_remote_device: the handle to the core remote device object for which
- * to build an IO request.
- * @io_tag: This parameter specifies the IO tag to be associated with this
- * request. If SCI_CONTROLLER_INVALID_IO_TAG is passed, then a copy of the
- * request is built internally. The request will be copied into the actual
- * controller request memory when the IO tag is allocated internally during
- * the scic_controller_start_io() method.
- * @user_io_request_object: This parameter specifies the user IO request to be
- * utilized during IO construction. This IO pointer will become the
- * associated object for the core IO request object.
- * @scic_io_request_memory: This parameter specifies the memory location to be
- * utilized when building the core request.
- * @new_scic_io_request_handle: This parameter specifies a pointer to the
- * handle the core will expect in further interactions with the core IO
- * request object.
- *
- * The SCI core implementation will create an association between the user IO
- * request object and the core IO request object. Indicate if the controller
- * successfully built the IO request. SCI_SUCCESS This value is returned if the
- * IO request was successfully built.
- */
enum sci_status scic_io_request_construct(
struct scic_sds_controller *scic_controller,
struct scic_sds_remote_device *scic_remote_device,
- u16 io_tag,
- void *user_io_request_object,
- struct scic_sds_request *scic_io_request_memory,
- struct scic_sds_request **new_scic_io_request_handle);
+ u16 io_tag, struct scic_sds_request *sci_req);
/**
* scic_io_request_construct_basic_ssp() - This method is called by the SCI