Re: how to handle QUEUE_FULL/SAM_STAT_TASK_SET_FULL in userspace?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2007-11-15 at 15:59 -0600, Chris Friesen wrote:
> Moore, Eric wrote:
> > On Thursday, November 15, 2007 12:10 PM, Chris Friesen wrote:
> 
> >>Does this status mean that the command needs to be retried by the 
> >>userspace app, that it has already been retried by the lower 
> >>levels and 
> >>is now completed, or something else entirely?
> 
> > The midlayer is retrying the command.  I pointed you to the code in the
> > previous email.
> 
> James Smart just indicated that the midlayer was not retrying the 
> command because it's sgio.  Is he mistaken?

No.  When the command goes via SG_IO it bypasses all return status
processing (and QUEUE_FULL/BUSY is a return status).  When it's
submitted in the normal way (i.e. via a ULD) then the mid-layer
processes these returns to a retry strategy.

> If the midlayer is retrying the command, then what should the 
> application do when it receives that status?

James


-
To unsubscribe from this list: 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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux