From: "S. J. van Harmelen" <svh@dds.nl>
To: device-mapper development <dm-devel@redhat.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [PATCH 0/3] Workqueue framework and ALUA hardware handler
Date: Mon, 19 Nov 2007 08:51:56 +0100 [thread overview]
Message-ID: <1195458716.5873.1.camel@sanderbal> (raw)
In-Reply-To: <473C0DD0.7080702@suse.de>
Hi Hannes,
Can you tell me when these patches get in the kernel? Is that going to
be 2.6.24.x or can we expect them before that?
Sander
On Thu, 2007-11-15 at 10:13 +0100, Hannes Reinecke wrote:
> Hi all,
>
> this patchset adds some more abstraction to the multipath
> hardware handlers.
> - A generic workqueue framework is added, which allows the
> hardware handler to submit failover commands independent
> from multipath I/O.
> - The exsting RDAC hardware handler is converted to use that
> framework
> - A new SPC-3 ALUA hardware handler is added, using that
> framework
> - A controller abstraction is added to the framework, which
> allows for command throttling based on the used controller.
> - The RDAC hardware handler is modified to use the new
> controller framework.
>
> This patchset superseded my previous implementation of the
> SPC-3 ALUA handler.
> Next plans are to update the table definitions and multipath-tools
> to allow for a passing of the controller ID from userland; ALUA
> doesn't specify for any controller information, so we have to
> do this by hand based on prior knowledge of the storage array.
>
> As per normal, comments etc welcome.
>
> Cheers,
>
> Hannes
prev parent reply other threads:[~2007-11-19 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 9:13 [PATCH 0/3] Workqueue framework and ALUA hardware handler Hannes Reinecke
2007-11-19 7:51 ` S. J. van Harmelen [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=1195458716.5873.1.camel@sanderbal \
--to=svh@dds.nl \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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