public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/2] Evaluate TPGS setting for ALUA device handler
Date: Thu, 19 Mar 2009 03:41:08 -0700	[thread overview]
Message-ID: <1237459268.4138.57.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <49C1FCE0.3040808@suse.de>

On Thu, 2009-03-19 at 09:05 +0100, Hannes Reinecke wrote:
> The ALUA device handler should only be attached if the 'TPGS' setting
> in the inquiry structure indicates so. So we should be evaluating the
> 'tpgs' setting when trying to attach the ALUA device handler.
> This way we can get rid of the explicit device table in scsi_dh_alua
> and will support any ALUA capable device out-of-the-box.
> 
> This is a repost of the patchset send yesterday, including
> the suggestions from James B. to just pull the tpgs setting
> off the inquiry data instead of adding a new field in the
> scsi_device structure.

Hannes and co, these patches looks fine to me..   The plan on my side to
is start testing the scsi_dh_alua client changes againt the
lio-core-2.6.git implict ALUA logical unit group and target port group
bits for v2.6.30.  Getting the initial optimized <-> non optimize ALUA
state transitions up should be done in the next weeks for you to poke at
seriously against your scsi_dh_alua nodes using Open/iSCSI.  Also from
there the first explict ALUA using MO_SET_TARGET_PGS.

>From there target_core_mod PR and ALUA fabric against OpenFCoE target
ports and all sorts of Linux Cluster clients is not too far away.

:-)

--nab

> 
> Signed-off-by: Hannes Reinecke <hare@suse.de>


      reply	other threads:[~2009-03-19 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  8:05 [PATCH 0/2] Evaluate TPGS setting for ALUA device handler Hannes Reinecke
2009-03-19 10:41 ` Nicholas A. Bellinger [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=1237459268.4138.57.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@HansenPartnership.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