linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Nic Bellinger <nab@daterainc.com>
Cc: Doug Gilber <dgilbert@interlog.com>,
	target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/2] TCM Referrals support
Date: Wed, 16 Oct 2013 09:25:22 +0200	[thread overview]
Message-ID: <1381908324-82135-1-git-send-email-hare@suse.de> (raw)

Hi Nic,

I've finally bitten the bullet and implemented referrals
support for TCM. It has been on my to-do list for a long
time, but finally I've gotten around to actually _do_ anything about it.

TCM now will enable referrals support when an appropriate
map is being fed into 'lba_map'. Format there is:
  <segment size> <segment multiplier>
  <start lba> <end lba> <pgX:stateY> ... <pgN:stateM>
  ...
  
<pgX> is the number of the first target port group,
<stateY> is a character denominating the ALUA access state:
'O' for 'Active/Optimized', 'A' for 'Active/Non-Optimized',
'S' for 'Standby', and 'U' for 'Unavailable'.
For further details see SBC-3, Section 'Referrals'.
  
Yes, I know, it's far from perfect and violates the
'one item per attribute' rule. But breaking this
down into several attributes and ensure the update
is done consistently _and_ atomically is beyond my
configfs skills. So there.

Hannes Reinecke (2):
  target_core_alua: Referrals infrastructure
  target_core_alua: Referrals configfs integration

 drivers/target/target_core_alua.c      | 252 +++++++++++++++++++++++++++++++++
 drivers/target/target_core_alua.h      |  12 +-
 drivers/target/target_core_configfs.c  | 183 +++++++++++++++++++++++-
 drivers/target/target_core_device.c    |   3 +
 drivers/target/target_core_sbc.c       |   5 +-
 drivers/target/target_core_spc.c       |  20 +++
 drivers/target/target_core_transport.c |  28 +++-
 include/scsi/scsi.h                    |   1 +
 include/target/target_core_base.h      |  18 +++
 9 files changed, 517 insertions(+), 5 deletions(-)

-- 
1.7.12.4

             reply	other threads:[~2013-10-16  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  7:25 Hannes Reinecke [this message]
2013-10-16  7:25 ` [PATCH 1/2] target_core_alua: Referrals infrastructure Hannes Reinecke
2013-10-16 22:28   ` Nicholas A. Bellinger
2013-10-17  7:38     ` Hannes Reinecke
2013-10-16  7:25 ` [PATCH 2/2] target_core_alua: Referrals configfs integration Hannes Reinecke
2013-10-17  0:36   ` Nicholas A. Bellinger
2013-10-17  7:42     ` Hannes Reinecke

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=1381908324-82135-1-git-send-email-hare@suse.de \
    --to=hare@suse.de \
    --cc=dgilbert@interlog.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@daterainc.com \
    --cc=target-devel@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).