From: James Bottomley <James.Bottomley@SteelEye.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: "Moore, Eric" <Eric.Moore@lsi.com>,
"Stephens, Larry" <Larry.Stephens@lsi.com>,
linux-scsi@vger.kernel.org, dgilbert@interlog.com,
DL-MPT Fusion Linux <DL-MPTFusionLinux@lsi.com>
Subject: Re: how to handle QUEUE_FULL/SAM_STAT_TASK_SET_FULL in userspace?
Date: Thu, 15 Nov 2007 16:18:00 -0600 [thread overview]
Message-ID: <1195165080.9519.6.camel@localhost.localdomain> (raw)
In-Reply-To: <473CC148.9050106@nortel.com>
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
next prev parent reply other threads:[~2007-11-15 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 19:54 how to handle QUEUE_FULL/SAM_STAT_TASK_SET_FULL in userspace? Chris Friesen
2007-11-13 22:04 ` Chris Friesen
2007-11-13 22:34 ` Moore, Eric
2007-11-14 17:23 ` Chris Friesen
2007-11-14 22:45 ` Moore, Eric
2007-11-15 19:09 ` Chris Friesen
2007-11-15 19:43 ` James Smart
2007-11-15 19:59 ` Moore, Eric
2007-11-15 19:57 ` Moore, Eric
2007-11-15 21:59 ` Chris Friesen
2007-11-15 22:18 ` James Bottomley [this message]
2007-11-15 22:35 ` Moore, Eric
2007-11-15 22:47 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195165080.9519.6.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=Eric.Moore@lsi.com \
--cc=Larry.Stephens@lsi.com \
--cc=cfriesen@nortel.com \
--cc=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox