[SCSI] export scsi-ml functions needed by tgt_scsi_lib and its LLDs

This patch contains the needed changes to the scsi-ml for the target
mode support.

Note, per the last review we moved almost all the fields we added
to the scsi_cmnd to our internal data structure which we are going
to try and kill off when we can replace it with support from other
parts of the kernel.

The one field we left on was the offset variable. This is needed to handle
the case where the target gets request that is so large that it cannot
execute it in one dma operation. So max_secotors or a segment limit may
limit the size of the transfer. In this case our tgt core code will
break up the command into managable transfers and send them to the
LLD one at a time. The offset is then used to tell the LLD where in
the command we are at. Is there another field on the scsi_cmd for
that?

Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

1 files changed, 43 insertions, 0 deletions

diff --git a/include/scsi/scsi_host.h b/include/scsi/scsi_host.h
index 6d8945d71c65..7f1f411d07af 100644
--- a/include/scsi/scsi_host.h
+++ b/include/scsi/scsi_host.h
@@ -7,6 +7,7 @@
 #include <linux/workqueue.h>
 #include <linux/mutex.h>
 
+struct request_queue;
 struct block_device;
 struct completion;
 struct module;
@@ -124,6 +125,39 @@ struct scsi_host_template {
                              void (*done)(struct scsi_cmnd *));
 
         /*
+         * The transfer functions are used to queue a scsi command to
+         * the LLD. When the driver is finished processing the command
+         * the done callback is invoked.
+         *
+         * return values: see queuecommand
+         *
+         * If the LLD accepts the cmd, it should set the result to an
+         * appropriate value when completed before calling the done function.
+         *
+         * STATUS: REQUIRED FOR TARGET DRIVERS
+         */
+        /* TODO: rename */
+        int (* transfer_response)(struct scsi_cmnd *,
+                                  void (*done)(struct scsi_cmnd *));
+        /*
+         * This is called to inform the LLD to transfer cmd->request_bufflen
+         * bytes of the cmd at cmd->offset in the cmd. The cmd->use_sg
+         * speciefies the number of scatterlist entried in the command
+         * and cmd->request_buffer contains the scatterlist.
+         *
+         * If the command cannot be processed in one transfer_data call
+         * becuase a scatterlist within the LLD's limits cannot be
+         * created then transfer_data will be called multiple times.
+         * It is initially called from process context, and later
+         * calls are from the interrup context.
+         */
+        int (* transfer_data)(struct scsi_cmnd *,
+                              void (*done)(struct scsi_cmnd *));
+
+        /* Used as callback for the completion of task management request. */
+        int (* tsk_mgmt_response)(u64 mid, int result);
+
+        /*
          * This is an error handling strategy routine.  You don't need to
          * define one of these if you don't want to - there is a default
          * routine that is present that should work in most cases.  For those
@@ -589,6 +623,12 @@ struct Scsi_Host {
          */
         unsigned int max_host_blocked;
 
+        /*
+         * q used for scsi_tgt msgs, async events or any other requests that
+         * need to be processed in userspace
+         */
+        struct request_queue *uspace_req_q;
+
         /* legacy crap */
         unsigned long base;
         unsigned long io_port;
@@ -687,6 +727,9 @@ extern void scsi_unblock_requests(struct Scsi_Host *);
 extern void scsi_block_requests(struct Scsi_Host *);
 
 struct class_container;
+
+extern struct request_queue *__scsi_alloc_queue(struct Scsi_Host *shost,
+                                                void (*) (struct request_queue *));
 /*
  * These two functions are used to allocate and free a pseudo device
  * which will connect to the host adapter itself rather than any