[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: [dm-devel] Re: [PATCH 7/7] scsi_dh: attach to hardware handler fromdm-mpath
- From: Chandra Seetharaman <sekharan us ibm com>
- To: Shyam_Iyer Dell com
- Cc: James Bottomley HansenPartnership com, dm-devel redhat com, linux-scsi vger kernel org
- Subject: RE: [dm-devel] Re: [PATCH 7/7] scsi_dh: attach to hardware handler fromdm-mpath
- Date: Mon, 19 May 2008 13:01:43 -0700
Shyam,
Yes, the usefulness is understood. Hannes made that available thru the
dh_state parameter (2/7 of this series).
Just an FYI.
chandra
On Tue, 2008-05-20 at 00:41 +0530, Shyam_Iyer Dell com wrote:
> >Chandra Seetharaman wrote:
> >> Hence, there is no need to attach it again from the multipath layer.
>
> Hannes Reinecke wrote:
> >Yes, you do. The user might have it's own custom configuration file,
> covering new/unknown/unhandled/testing devices, which out of necessity
> are _not_
> >hardcoded in the device table of the device handler.
> >So multipath has to have a way of attaching device handler to those
> devices, too.
>
> Quite agree. There are a lot of OEM vendors that may use for example the
> LSI RDAC conrtoller but the SCSI inquiry for these devices return the
> OEM device names.
> The DELL MD3000 is an example of such a box. Instead of hardcoding
> device tables of the handler if they could be configured using a custom
> configuration file enabling new hardware becomes such a bliss.
>
> -Shyam Iyer
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]