SCSI Generic version 4 interface, release 1.2

that? ChangeLog for release 1.2 [20070314] - add dout_resid - re-arrange uint64_t types (i.e. pointer carriers) to be on a 8 byte boundary - reinstate dout_iovec_count and din_iovec_count (they were in release 1.1 but bsg dropped them) - change name: response_len_wr

RFC: add transport host byte values and common failure behavior

iSCSI and FC classes and drivers have several similarities in how they handle transport problems. But between them and among the drivers there are also several differences, all of which make configuring them a little more fun they they need to be. The following patches attempt to begin to

[PATCH 3/4] iscsi class, libiscsi and qla4xxx: convert to new transport host byte values

From: Mike Christie [EMAIL PROTECTED] This patch converts the iscsi drivers to the new host byte values Signed-off-by: Mike Christie [EMAIL PROTECTED] --- drivers/scsi/libiscsi.c | 21 - drivers/scsi/qla4xxx/ql4_isr.c |2 +-

[PATCH 2/4] scsi: add transport host byte errors

From: Mike Christie [EMAIL PROTECTED] Small guide to differences in iscsi and fc: I_T nexus or port we are connected to at some other end point iscsi: iscsi_session fc: rport fast_io_fail_tmo iscsi: session recovery_tmo fc: rport fast_io_fail_tmo The difference is that when the timer fires,

Re: [PATCH 2/4] scsi: add transport host byte errors

[EMAIL PROTECTED] wrote: The following patches attempt unify what upper layers will see drivers like multipath can make a good guess. This relies on drivers being Oops, I mean to say with the patches upper layers like multipath will see common behavior from LLDs hooked into transport classes.

Re: [PATCH 2/4] scsi: add transport host byte errors

[EMAIL PROTECTED] wrote: When using multipath and the fast_io_fail_tmo fires then the class can fail commands with DID_TRANSPORT_FAILFAST or drivers can use Bah, that is going to be wrong or ugly for tape commands. We would want to add another new value, DID_TRANSPORT_ABORTED which would check