linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	device-mapper development <dm-devel@redhat.com>
Subject: [PATCH 0/7] scsi_dh framework update take #2
Date: Tue, 20 May 2008 16:04:27 +0200	[thread overview]
Message-ID: <4832DA6B.3050702@suse.de> (raw)

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
-- 
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-20 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 14:04 Hannes Reinecke [this message]
2008-05-23  2:08 ` [PATCH 0/7] scsi_dh framework update take #2 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=4832DA6B.3050702@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --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 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).