linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 0/7] scsi_dh framework update take #2
Date: Thu, 22 May 2008 19:08:10 -0700	[thread overview]
Message-ID: <1211508490.21974.500.camel@chandra-ubuntu> (raw)
In-Reply-To: <4832DA6B.3050702@suse.de>

Hi Hannes,

I looked at the patches except 3, 4 and 5 (as I don't have context
knowledge).

Thanks,

chandra
On Tue, 2008-05-20 at 16:04 +0200, Hannes Reinecke wrote:
> Hi James,
> 
> this is the second repost of my patchset to update the scsi_dh
> infrastructure. It includes the comments by Chandra.
> 
> It's based on the current scsi-misc tree.
> 
> Main features of the patchset are:
> - Use a single callback for the notifier chain
> - Merge all device maps into a single list,
>  which will be scanned by a generic function
> - Add a sysfs attribute 'dh_state' for each sdev
> - Add a generic SPC-3 ALUA device handler
> - Update device handlers to check if the
>  device actually supports this handler.
>  When attaching manually we are able to attach
>  to basically any device, so we have to make sure
>  that the device handler is actually supported.
> - Manually attach a device when a hardware handler
>  is specified; this allows multipath to override
>  the built-in hardware table.
> - Update dm-multipath to explicitly attach to
>  the specified device handler. This allows
>  overriding of the built-in table by the
>  multipath values.
> 
> As per usual, comment etc are welcome.
> 
> Cheers,
> 
> Hannes


      reply	other threads:[~2008-05-23  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 14:04 [PATCH 0/7] scsi_dh framework update take #2 Hannes Reinecke
2008-05-23  2:08 ` Chandra Seetharaman [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=1211508490.21974.500.camel@chandra-ubuntu \
    --to=sekharan@us.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --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 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).