* [PATCH 0/3] Update scsi_dh infrastructure
@ 2008-05-07 15:03 Hannes Reinecke
2008-05-07 18:45 ` Chandra Seetharaman
0 siblings, 1 reply; 3+ messages in thread
From: Hannes Reinecke @ 2008-05-07 15:03 UTC (permalink / raw)
To: Chandra Seetharaman; +Cc: James Bottomley, SCSI Mailing List
Hi Chandra,
this patchset updates the scsi_dh infrastructure as laid out
in my previous mail. In particular it does
- update the scsi_dh infrastructure to implement a generic
device table handling; the static device tables from the
individual handlers are copied into a generic list.
This allows us to do the checking in the main scsi_dh
module instead of having to implement it for every handler.
And we can then modify this list dynamically
- Implements a 'dh_state' attribute for the sdev, which
allows for manipulating of the device handler itself.
So we can now attach, detach, and activate any device
handler manually.
- And finally I've updated my SPC-3 alua handler for the
new infrastructure. Please include it in your patchset, too.
Patches are relative to your latest patchset.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 0/3] Update scsi_dh infrastructure
2008-05-07 15:03 [PATCH 0/3] Update scsi_dh infrastructure Hannes Reinecke
@ 2008-05-07 18:45 ` Chandra Seetharaman
2008-05-08 6:31 ` Hannes Reinecke
0 siblings, 1 reply; 3+ messages in thread
From: Chandra Seetharaman @ 2008-05-07 18:45 UTC (permalink / raw)
To: Hannes Reinecke; +Cc: James Bottomley, SCSI Mailing List, dm-devel
Hannes,
I do not see the patch :)
chandra
On Wed, 2008-05-07 at 17:03 +0200, Hannes Reinecke wrote:
> Hi Chandra,
>
> this patchset updates the scsi_dh infrastructure as laid out
> in my previous mail. In particular it does
>
> - update the scsi_dh infrastructure to implement a generic
> device table handling; the static device tables from the
> individual handlers are copied into a generic list.
> This allows us to do the checking in the main scsi_dh
> module instead of having to implement it for every handler.
> And we can then modify this list dynamically
> - Implements a 'dh_state' attribute for the sdev, which
> allows for manipulating of the device handler itself.
> So we can now attach, detach, and activate any device
> handler manually.
> - And finally I've updated my SPC-3 alua handler for the
> new infrastructure. Please include it in your patchset, too.
>
> Patches are relative to your latest patchset.
>
> Cheers,
>
> Hannes
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 0/3] Update scsi_dh infrastructure
2008-05-07 18:45 ` Chandra Seetharaman
@ 2008-05-08 6:31 ` Hannes Reinecke
0 siblings, 0 replies; 3+ messages in thread
From: Hannes Reinecke @ 2008-05-08 6:31 UTC (permalink / raw)
To: sekharan; +Cc: James Bottomley, SCSI Mailing List, dm-devel
Hi Chandra,
Chandra Seetharaman wrote:
> Hannes,
>
> I do not see the patch :)
>
Argl. They got stuck in the mailqueue.
Here they are.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-05-08 6:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-07 15:03 [PATCH 0/3] Update scsi_dh infrastructure Hannes Reinecke
2008-05-07 18:45 ` Chandra Seetharaman
2008-05-08 6:31 ` Hannes Reinecke
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox