linux-toradex.git/include/scsi/scsi_cmnd.h, branch v3.2.48

[SCSI] Deprecate SCSI_PROT_*_CONVERT operations

2009-10-02T14:46:25+00:00

The checksum format is orthogonal to whether the protection information
is being passed on beyond the HBA or not.  It is perfectly valid to use
a non-T10 CRC with WRITE_STRIP and READ_INSERT.

Consequently it no longer makes sense to explicitly refer to the
conversion in the protection operation.  Update sd_dif and lpfc
accordingly.

Signed-off-by: Martin K. Petersen 
Acked-by: Ihab Hamadi 
Signed-off-by: James Bottomley

block: convert to pos and nr_sectors accessors

2009-05-11T07:50:54+00:00

With recent cleanups, there is no place where low level driver
directly manipulates request fields.  This means that the 'hard'
request fields always equal the !hard fields.  Convert all
rq->sectors, nr_sectors and current_nr_sectors references to
accessors.

While at it, drop superflous blk_rq_pos() < 0 test in swim.c.

[ Impact: use pos and nr_sectors accessors ]

Signed-off-by: Tejun Heo 
Acked-by: Geert Uytterhoeven 
Tested-by: Grant Likely 
Acked-by: Grant Likely 
Tested-by: Adrian McMenamin 
Acked-by: Adrian McMenamin 
Acked-by: Mike Miller 
Cc: James Bottomley 
Cc: Bartlomiej Zolnierkiewicz 
Cc: Borislav Petkov 
Cc: Sergei Shtylyov 
Cc: Eric Moore 
Cc: Alan Stern 
Cc: FUJITA Tomonori 
Cc: Pete Zaitcev 
Cc: Stephen Rothwell 
Cc: Paul Clements 
Cc: Tim Waugh 
Cc: Jeff Garzik 
Cc: Jeremy Fitzhardinge 
Cc: Alex Dubov 
Cc: David Woodhouse 
Cc: Martin Schwidefsky 
Cc: Dario Ballabio 
Cc: David S. Miller 
Cc: Rusty Russell 
Cc: unsik Kim 
Cc: Laurent Vivier 
Signed-off-by: Jens Axboe

[SCSI] Make scsi.h independent of the rest of the scsi includes

2009-03-12T17:58:13+00:00

This allows it to compile and be used on the ps3 platform that wants
to use the #define values in scsi.h without actually having
CONFIG_SCSI set.

Signed-off-by: James Bottomley

block: unify request timeout handling

2008-10-09T06:56:13+00:00

Right now SCSI and others do their own command timeout handling.
Move those bits to the block layer.

Instead of having a timer per command, we try to be a bit more clever
and simply have one per-queue. This avoids the overhead of having to
tear down and setup a timer for each command, so it will result in a lot
less timer fiddling.

Signed-off-by: Mike Anderson 
Signed-off-by: Jens Axboe

[SCSI] Support devices with protection information

2008-07-26T19:14:55+00:00

Implement support for DMA of protection information for devices that
are data integrity capable.

 - Add support for mapping an extra scatter-gather list containing
   the protection information.

 - Allocate protection scsi_data_buffer if host is DIX (integrity DMA)
   capable.

 - Accessor function for checking whether a device has protection
   enabled.

Signed-off-by: Martin K. Petersen 
Signed-off-by: James Bottomley

[SCSI] Command protection operation

2008-07-26T19:14:54+00:00

Controllers that support DMA of protection information must be told
explicitly how to handle the I/O.  The controller has no knowledge of
the protection capabilities of the target device so this information
must be passed in the scsi_cmnd.

 - The protection operation tells the HBA whether to generate, strip or
   verify protection information.

 - The protection type tells the HBA which layout the target is
   formatted with.  This is necessary because the controller must be
   able to correctly interpret the included protection information in
   order to verify it.

 - When a scsi_cmnd is reused for error handling the protection
   operation must be cleared and saved while error handling is in
   progress.

 - prot_op and prot_type are placed in an existing hole in scsi_cmnd
   and don't cause the structure to grow.

Signed-off-by: Martin K. Petersen 
Signed-off-by: James Bottomley

[SCSI] scsi_cmnd.h: remove double inclusion of linux/blkdev.h

2008-07-12T13:22:37+00:00

Signed-off-by: Alexander Beregalov 
Signed-off-by: James Bottomley

[SCSI] add support for variable length extended commands

2008-05-02T16:33:25+00:00

Add support for variable-length, extended, and vendor specific
CDBs to scsi-ml. It is now possible for initiators and ULD's
to issue these types of commands. LLDs need not change much.
All they need is to raise the .max_cmd_len to the longest command
they support (see iscsi patch).

- clean-up some code paths that did not expect commands to be
  larger than 16, and change cmd_len members' type to short as
  char is not enough.

Signed-off-by: Boaz Harrosh 
Signed-off-by: Benny Halevy 
Signed-off-by: James Bottomley

[SCSI] Let scsi_cmnd->cmnd use request->cmd buffer

2008-05-02T15:18:22+00:00

 - struct scsi_cmnd had a 16 bytes command buffer of its own.
   This is an unnecessary duplication and copy of request's
   cmd. It is probably left overs from the time that scsi_cmnd
   could function without a request attached. So clean that up.

 - Once above is done, few places, apart from scsi-ml, needed
   adjustments due to changing the data type of scsi_cmnd->cmnd.

 - Lots of drivers still use MAX_COMMAND_SIZE. So I have left
   that #define but equate it to BLK_MAX_CDB. The way I see it
   and is reflected in the patch below is.
   MAX_COMMAND_SIZE - means: The longest fixed-length (*) SCSI CDB
                      as per the SCSI standard and is not related
                      to the implementation.
   BLK_MAX_CDB.     - The allocated space at the request level

 - I have audit all ISA drivers and made sure none use ->cmnd in a DMA
   Operation. Same audit was done by Andi Kleen.

(*)fixed-length here means commands that their size can be determined
   by their opcode and the CDB does not carry a length specifier, (unlike
   the VARIABLE_LENGTH_CMD(0x7f) command). This is actually not exactly
   true and the SCSI standard also defines extended commands and
   vendor specific commands that can be bigger than 16 bytes. The kernel
   will support these using the same infrastructure used for VARLEN CDB's.
   So in effect MAX_COMMAND_SIZE means the maximum size command
   scsi-ml supports without specifying a cmd_len by ULD's

Signed-off-by: Boaz Harrosh 
Signed-off-by: James Bottomley

[SCSI] export command allocation and freeing functions independently of the host

2008-04-07T17:18:57+00:00

This is needed by things like USB storage that want to set up static
commands for later use at start of day.

Signed-off-by: James Bottomley