On Sun, Jul 02, 2006 at 04:47:58PM +0300, Erez Zilber wrote: > Ishai Rabinovitz wrote: > >On Sun, Jul 02, 2006 at 01:51:51PM +0300, Erez Zilber wrote: > > > Did you find any ref for this in SAM3? The only thing that I was able to > find there is that a target that receives an "abort task" has to send a > task management response even if it has already sent a SCSI response for > that task. > > Thanks > Erez I'm using this feature (After the response to the ABORT I'm checking if I got a response to the original request meanwhile). In any case I think it is more efficient to handle the response and not the abort. It is safe for read requests. and I think it is safe also for write requests since the target must have handled the request before handling the abort (Otherwise there would have been no response to the request). Does anyone see a problem with that (Maybe with Multipath)? -- Ishai Rabinovitz - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
