linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: sekharan@us.ibm.com
Cc: James Bottomley <James.Bottomley@HansenPartnership.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: Mon, 19 May 2008 12:21:36 +0200	[thread overview]
Message-ID: <483154B0.7020500@suse.de> (raw)
In-Reply-To: <1210964001.21974.351.camel@chandra-ubuntu>

Hi Chandra,

Chandra Seetharaman wrote:
> On Thu, 2008-05-15 at 11:46 +0200, Hannes Reinecke wrote:
>> Hi Chandra,
>>
>> Chandra Seetharaman wrote:
>>> What is the purpose of this feature ?
>>>
>>> With dh_state functionality, one could associate a handler to a new
>>> device and then if one does "multipath", the hardware handler would be
>>> associated with the multipath device. What are we achieving by this ?
>>>
>> This allows multipath to override the device tables build into
>> the device handler. Reason here is that multipath has a configuration
>> file which allows the user to override the build-in defaults.
>> And this includes the hardware handler, so we need to make sure that
>> the hardware handler is indeed attached.
> 
> Hardware handler's existence is currently been verified during parsing
> (by doing a request_module() followed by scsi_dh_handler_exist() in
> parse_hw_handler()).
> 
Yes, but this only verifies that the _handler_ exist, not that it is
attached to this sdev

> Hardware handler module is attached to the device itself (thru
> try_module_get() in attach), so, the module will exist as long as the
> device exists.
> 
Not quite. It's only attached automatically if the device map has
an entry for this module.
However, given this patchset we can now easily manually attach any
device to the device handler. Or at least try to do so.
It's then up to the device handler to refuse binding if none of
the necessary pages/information etc. was found.

> Hence, there is no need to attach it again from the multipath layer.
> 
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.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-05-19 10:21 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 [this message]
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
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=483154B0.7020500@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dm-devel@redhat.com \
    --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).