From: Brian King <brking@us.ibm.com>
To: James.Bottomley@steeleye.com
Cc: linux-scsi@vger.kernel.org
Subject: [PATCH] IBM Power RAID driver - third version
Date: Wed, 25 Feb 2004 15:03:58 -0600 [thread overview]
Message-ID: <403D0DBE.4020207@us.ibm.com> (raw)
I have uploaded the third version of the ipr device driver to:
http://www-124.ibm.com/storageio/ipr/patch-2.6.3-ipr-2.0.0-6.gz
Major changes:
1. Removed use of bit fields.
2. Removed show_queue_depth since we can use default one.
3. Added FIXME comments to issues still outstanding that
require midlayer changes
4. Several bug fixes.
Outstanding issues:
1. Driver needs the start_unit patch I submitted in order to function
properly. This has still not been accepted. A 2.6.3 patch can be
found at: http://www-124.ibm.com/storageio/ipr/patch-2.6.3-start_unit.gz
2. Driver needs the array_controller patch, which still has not been
accepted. http://www-124.ibm.com/storageio/ipr/patch-2.6.3-array_controller.gz
3. Still checking allow_cmds flag in queuecommand. ERP ops (e.g. TUR),
still do not check host_blocked. Patch to force retries to obey
host_blocked flag has been accepted, will be submitting another
patch to fix ERP ops. Once this is accepted, I will remove the check.
4. ioa_is_dead flag still exists and is checked in queuecommand. Need to
add a scsi_set_host_offline interface to change this.
5. res->del_from_ml flag still exists. To remove it requires a
scsi_set_device_offline interface.
6. Driver is still modifying the command timeout. Once an acceptable
alternative is agreed upon, this can be cleaned up.
Please apply. I will continue working the outstanding issues and
update the ipr driver along with the rest of the patch.
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next reply other threads:[~2004-02-25 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 21:03 Brian King [this message]
2004-02-27 19:39 ` [PATCH] IBM Power RAID driver - third version Brian King
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=403D0DBE.4020207@us.ibm.com \
--to=brking@us.ibm.com \
--cc=James.Bottomley@steeleye.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).