From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Hannes Reinecke <hare@suse.de>
Cc: sekharan@us.ibm.com, linux-scsi <linux-scsi@vger.kernel.org>,
dm-devel <dm-devel@redhat.com>
Subject: Re: [PATCH 7/7] scsi_dh: attach to hardware handler from dm-mpath
Date: Thu, 22 May 2008 09:14:54 +0100 [thread overview]
Message-ID: <1211444095.3956.6.camel@localhost.localdomain> (raw)
In-Reply-To: <4833BEB2.1070305@suse.de>
On Wed, 2008-05-21 at 08:18 +0200, Hannes Reinecke wrote:
> Chandra Seetharaman wrote:
> > Hi Hannes,
> >
> > Now I see why you want this change in dm-multipath. I think I agree with
> > these changes.
> >
> Ah. good.
>
> > But, it brings another question: what does dh_state provide ? Help to
> > user to see which hardware handler a device is attached to ?
> >
> And allowing to attach to a different hardware handler.
> Not everyone is running multipathing, but might be interested in the
> having the device handler nevertheless.
>
> > I thought more about the scsi_dh_detach function (in the context of my
> > earlier comment), adding it would require more housekeeping to associate
> > one-to-one mapping between attach and detach. We can leave it the same
> > way as the module will be detached when the device disappear eventually.
> >
> Why? You can detach with dh_state, too; just do an
>
> echo detach > /sys/block/sdX/device/dh_state
>
> and the hardware handler will detach.
> So no additional attribute is required.
Actually, if you're going down this route, it makes more sense to have
the device handler be a driver ... remember you were the one promising
multiple driver binding at the FS/Storage summit ... that way we can
use all the generic driver standard interfaces for manual
binding/unbinding. Plus we can place the attributes as driver attribute
groups.
James
next prev parent reply other threads:[~2008-05-22 23:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 14:43 [PATCH 7/7] scsi_dh: attach to hardware handler from dm-mpath Hannes Reinecke
2008-05-15 2:50 ` Chandra Seetharaman
2008-05-15 9:46 ` Hannes Reinecke
2008-05-16 18:53 ` Chandra Seetharaman
2008-05-19 10:21 ` Hannes Reinecke
2008-05-19 18:20 ` Chandra Seetharaman
2008-05-20 12:41 ` Hannes Reinecke
2008-05-20 18:52 ` Chandra Seetharaman
2008-05-21 6:18 ` Hannes Reinecke
2008-05-22 8:14 ` James Bottomley [this message]
2008-05-23 11:40 ` Hannes Reinecke
2008-05-23 14:06 ` James Bottomley
2008-05-19 19:11 ` [dm-devel] Re: [PATCH 7/7] scsi_dh: attach to hardware handler fromdm-mpath Shyam_Iyer
2008-05-19 20:01 ` Chandra Seetharaman
-- strict thread matches above, loose matches on Subject: below --
2008-05-20 14:05 [PATCH 7/7] scsi_dh: attach to hardware handler from dm-mpath Hannes Reinecke
2008-05-23 2:08 ` 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=1211444095.3956.6.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=sekharan@us.ibm.com \
/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).