linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, agk@redhat.com, babu.moger@netapp.com,
	sekharan@us.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/3] dm mpath: add support for using previously attached scsi_dh
Date: Tue, 08 May 2012 18:20:45 +0200	[thread overview]
Message-ID: <4FA947DD.8060908@suse.de> (raw)
In-Reply-To: <20120508140541.GB8383@redhat.com>

On 05/08/2012 04:05 PM, Mike Snitzer wrote:
> On Tue, May 08 2012 at  2:22am -0400,
> Hannes Reinecke<hare@suse.de>  wrote:
>
>> On 05/08/2012 05:19 AM, Mike Snitzer wrote:
>>> Use the previously attached scsi_dh if "default" is provided as the
>>> hardware handler name (the new 'use_default_hw_handler' flag is set in
>>> the multipath structure).
>>>
>>> Leverage scsi_dh_attach's ability to increment the scsi_dh's reference
>>> count if the same scsi_dh name is provided when attaching -- currently
>>> attached scsi_dh name is determined with scsi_dh_attached_handler_name.
>>>
>> Not sure it that's the correct way.
>>
>> Using 'default' as the hardware handler name has the drawback that
>> the original information (ie the original hardware handler name)
>> is lost.
>
> BTW, on this point: How is the original handler's name lost with my
> patches?  I set m->hw_handler_name to the original (aka attached)
> handler's name (as returned scsi_dh_attached_handler_name).
>
> "default" is only used as a key to trigger the use of the attached
> handler (it causes m->use_default_hw_handler to be set).
>
What I meant is that within multipath you can only specify one hardware 
handler. So if it's 'default' and no hardware handler is attached we 
wouldn't know what to look for.

> Was my description or code somehow unclear?  Guess so... otherwise I'd
> not be clarifying this... unfortunately I'm not seeing where I fell
> short.
>
Meanwhile I've sent the patchset, Please check that for details.

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:[~2012-05-08 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08  3:19 [PATCH 2/3] scsi_dh: add scsi_dh_attached_handler_name Mike Snitzer
2012-05-08  3:19 ` [PATCH 3/3] dm mpath: add support for using previously attached scsi_dh Mike Snitzer
2012-05-08  6:22   ` Hannes Reinecke
2012-05-08 13:36     ` Mike Snitzer
2012-05-08 14:05     ` Mike Snitzer
2012-05-08 16:20       ` Hannes Reinecke [this message]

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=4FA947DD.8060908@suse.de \
    --to=hare@suse.de \
    --cc=agk@redhat.com \
    --cc=babu.moger@netapp.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sekharan@us.ibm.com \
    --cc=snitzer@redhat.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).