public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: dm-devel@redhat.com, linux-scsi@vger.kernel.org
Cc: andmike@us.ibm.com, michaelc@cs.wisc.edu,
	Chandra Seetharaman <sekharan@us.ibm.com>,
	James.Bottomley@HansenPartnership.com, jens.axboe@oracle.com,
	agk@redhat.com
Subject: [PATCH 0/7] Move hardware handlers from dm layer to SCSI layer
Date: Wed, 27 Feb 2008 17:08:28 -0800	[thread overview]
Message-ID: <20080228010828.5535.74088.sendpatchset@localhost.localdomain> (raw)

Hello,

Set of patches that follow this email facilitate movement of hardware
handlers from dm layer to SCSI layer.

Previous set of patches that implemented this was posted on Jan 24:
http://marc.info/?l=linux-scsi&m=120113462706925&w=2

Changes have been made based on feedback received from James, Alasdair,
Mike Christie and Mike Anderson.

Following are the changes:
 - Removed scsi_dh hardware handler in the dm layer. This means 
   no change (not even a change in the multipath.conf file) is
   required in user space.
 - Replaced REQ_OP_LB_TRANSITION with an activate() function.
 - Removed the SDEV_PASSIVE and added a prep_fn to the device 
   handler, hence giving it the veto power.
 - Replaced blk_execute_rq_nowait() with blk_execute_rq() in
   device handlers to make them synchronous. Added a thread(work queue)
   to dm-multipath to handle requests asynchronously.
 - Added Ed's changes to the EMC hardware handler.
   
Patches are created on top of 2.6.25-rc2-mm1.

Testing has been done with a IBM DS4800 storage device, which means the
infrastructure and the lsi_rdac hardware handler has been tested. Testing
by someone with the EMC hardware and/or HP hardware would be appreciated.

Comments, suggestions solicited.

Thanks,

chandra


-- 

----------------------------------------------------------------------
    Chandra Seetharaman               | Be careful what you choose....
              - sekharan@us.ibm.com   |      .......you may get it.
----------------------------------------------------------------------

             reply	other threads:[~2008-02-28  1:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28  1:08 Chandra Seetharaman [this message]
2008-02-28  1:08 ` [PATCH 1/7] scsi_dh: add skeleton for SCSI Device Handlers Chandra Seetharaman
2008-03-04 21:37   ` James Bottomley
2008-03-04 22:25     ` Chandra Seetharaman
2008-02-28  1:08 ` [PATCH 2/7] scsi_dh: add lsi rdac device handler Chandra Seetharaman
2008-02-28  1:08 ` [PATCH 3/7] scsi_dh: add hp sw " Chandra Seetharaman
2008-02-28  1:08 ` [PATCH 4/7] scsi_dh: add EMC Clariion " Chandra Seetharaman
2008-02-28  1:08 ` [PATCH 5/7] scsi_dh: Use SCSI device handler in dm-multipath Chandra Seetharaman
2008-02-28  1:09 ` [PATCH 6/7] scsi_dh: Remove hardware handlers from dm Chandra Seetharaman
2008-02-28  1:09 ` [PATCH 7/7] 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=20080228010828.5535.74088.sendpatchset@localhost.localdomain \
    --to=sekharan@us.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=agk@redhat.com \
    --cc=andmike@us.ibm.com \
    --cc=dm-devel@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