From: Chandra Seetharaman <sekharan@us.ibm.com>
To: linux-scsi@vger.kernel.org
Cc: dm-devel@redhat.com, andmike@us.ibm.com, michaelc@cs.wisc.edu,
agk@redhat.com, James.Bottomley@HansenPartnership.com,
jens.axboe@oracle.com, dwysocha@redhat.com,
Benoit_Arthur@emc.com, asson_ronald@emc.com,
Chandra Seetharaman <sekharan@us.ibm.com>
Subject: [PATCH 00/10] scsi_dh: Move hardware handlers from dm to SCSI
Date: Thu, 01 May 2008 14:49:41 -0700 [thread overview]
Message-ID: <20080501214941.27759.95121.sendpatchset@chandra-ubuntu> (raw)
Hello,
This is the latest version of the patchset that was posted on Apr 17:
http://marc.info/?l=linux-scsi&m=120847097122545&w=2
Following are the changes made since last post:
Based on Alasdair's comments:
- Split the dm-mpath patch into 4 patches to enhance readabilty
- Added comments to patch header and inline
- Added an interface scsi_dh_handler_exist() and used it
to verify the availability of a hardware handler
- Do not accept arguments with the hardware handler parameter
- Make the workqueue single threaded, and change its name
- removed the usage of path_to_activate and used an existing field
-renamed activate_passive_path to activate_path
- Bring back the pg_init_retries.
Others:
- Added additional devices to the device list
- removed few erroneous BUG assertions
- Fixed an erroneous return code from scsi_dh_rdac.c.
This patch set applies on 2.6.25-mm1.
This patch set has been tested on a DS4800.
Testing has been done earlier with the following storage devices:
- IBM DS4800 storage device for the lsi_rdac hardware handler
- HP storage device for the hp_sw hardware handler.
Thanks to Dave(dwysocha@redhat.com)
- EMC storage device for the EMC hardware handler.
Thanks to Arthur(Benoit_Arthur@emc.com) and Ronald(asson_ronald@emc.com)
In effect all hardware handlers are tested.
-------------------- Comment from Patch 01/10 ---------------------
Some of the storage devices (that can be accessed through multiple paths),
do need some special handling for
1. Activating the passive path of the storage access.
2. Decode and handle the special sense codes returned by the devices.
3. Handle the I/Os being sent to the passive path, especially
during the device probe time.
when accessed through multiple paths.
As of today this special device handling is done at the dm-multipath
layer using dm-handlers. That works well for (1); for (2) to be handled
at dm layer, scsi sense information need to be exported from SCSI to dm-layer,
which is not very attractive; (3) cannot be done at all at the dm layer.
Device handler has been moved to SCSI mainly to handle (2) and (3) properly.
----------------------
Thanks,
chandra
next reply other threads:[~2008-05-01 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 21:49 Chandra Seetharaman [this message]
2008-05-01 21:49 ` [PATCH 01/10] scsi_dh: add infrastructure for SCSI Device Handlers Chandra Seetharaman
2008-05-01 21:49 ` [PATCH 02/10] scsi_dh: add lsi rdac device handler Chandra Seetharaman
2008-05-01 21:49 ` [PATCH 03/10] scsi_dh: add hp sw " Chandra Seetharaman
2008-05-01 21:50 ` [PATCH 04/10] scsi_dh: add EMC Clariion " Chandra Seetharaman
2008-05-01 21:50 ` [PATCH 05/10] scsi_dh: Use SCSI device handler in dm-multipath Chandra Seetharaman
2008-05-01 21:50 ` [PATCH 06/10] scsi_dh: Do not allow arguments for hardware handlers Chandra Seetharaman
2008-05-02 22:47 ` Alasdair G Kergon
2008-05-03 0:01 ` [dm-devel] " Chandra Seetharaman
2008-05-01 21:50 ` [PATCH 07/10] scsi_dh: Add a single threaded workqueue for initializing paths Chandra Seetharaman
2008-05-01 21:50 ` [PATCH 08/10] scsi_dh: Remove dm_pg_init_complete Chandra Seetharaman
2008-05-01 21:50 ` [PATCH 09/10] scsi_dh: Remove hardware handlers from dm Chandra Seetharaman
2008-05-01 21:50 ` [PATCH 10/10] scsi_dh: Remove hardware handler infrastructure " Chandra Seetharaman
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=20080501214941.27759.95121.sendpatchset@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=Benoit_Arthur@emc.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=agk@redhat.com \
--cc=andmike@us.ibm.com \
--cc=asson_ronald@emc.com \
--cc=dm-devel@redhat.com \
--cc=dwysocha@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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