From: "Chris Friesen" <cfriesen@nortel.com>
To: Larry.Stephens@lsi.com
Cc: linux-scsi@vger.kernel.org, dgilbert@interlog.com,
James.Bottomley@SteelEye.com, Eric.Moore@lsi.com,
DL-MPTFusionLinux@lsi.com
Subject: Re: how to handle QUEUE_FULL/SAM_STAT_TASK_SET_FULL in userspace?
Date: Tue, 13 Nov 2007 16:04:03 -0600 [thread overview]
Message-ID: <473A1F53.2050209@nortel.com> (raw)
In-Reply-To: <4738AF7E.1060307@nortel.com>
Chris Friesen wrote:
> We recently moved from 2.6.10 to 2.6.14 and now we're seeing occasional
> QUEUE_FULL/SAM_STAT_TASK_SET_FULL errors being returned to userspace.
> These didn't ever show up in 2.6.10.
I found something that might be interesting.
With the the 3.01.18 fusion driver the queue length (as shown by
"/sys/class/scsi_generic/sgX/device/queue_depth") was set to 7, while
with the 3.02.57 fusion driver it was set to either 64 or 32.
It may be coincidence, but it's interesting that
MPT_SCSI_CMD_PER_DEV_LOW is set to 7 in the earlier driver, and 32 in
the later one, while MPT_SCSI_CMD_PER_DEV_HIGH went from 31 to 64.
Chris
next prev parent reply other threads:[~2007-11-13 22:04 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 [this message]
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
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=473A1F53.2050209@nortel.com \
--to=cfriesen@nortel.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Larry.Stephens@lsi.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;
as well as URLs for NNTP newsgroup(s).