All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: device-mapper development <dm-devel@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	christophe varoqui <christophe.varoqui@free.fr>
Subject: Re: Re: [PATCH] Add ALUA hardware handler
Date: Thu, 11 Oct 2007 12:47:29 -0500	[thread overview]
Message-ID: <470E61B1.4080007@cs.wisc.edu> (raw)
In-Reply-To: <470E5B37.1060902@cs.wisc.edu>

Just some thoughts

Mike Christie wrote:
>> This is actually by design. Problem here is the port group as returned by
>> REPORT TARGET PORT GROUPS does not have any association to the controller
>> which handles these ports.

So I agree the hw handler just knows that it has paths unless you do 
something like chandra and send commands to figure out the contoller 
mappings. But are you saying that in userspace during dm mpath device 
setup time, there is no way to figure out the mappings? We talked about 
making the controller mappings and handling the problem where you cannot 
flood the box and the problem of having to send multiple commands more 
generic. We did not do that for rdac at the time because we thought scsi 
hw handlers were going to be done sooner, and did not want to redo the 
effort, but if it helps it could be done.

  reply	other threads:[~2007-10-11 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 12:55 [PATCH] Add ALUA hardware handler Hannes Reinecke
2007-10-10 18:45 ` Mike Christie
2007-10-11  8:31   ` Hannes Reinecke
2007-10-11 17:19     ` Mike Christie
2007-10-11 17:47       ` Mike Christie [this message]
2007-10-11  2:08 ` [dm-devel] " 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=470E61B1.4080007@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=agk@redhat.com \
    --cc=christophe.varoqui@free.fr \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.