[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1249793762.11105.233.camel@haakon2.linux-iscsi.org>
Date: Sat, 08 Aug 2009 21:56:02 -0700
From: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To: LKML <linux-kernel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>
Cc: Douglas Gilbert <dgilbert@...erlog.com>,
Hannes Reinecke <hare@...e.de>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
Mike Christie <michaelc@...wisc.edu>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Andrew Morton <akpm@...ux-foundation.org>,
James Smart <James.Smart@...lex.Com>,
Philipp Reisner <philipp.reisner@...bit.com>
Subject: [PATCH 0/2] [Target_Core_Mod/Persistent_Reservations]: Add
SPEC_I_PT=1 support
Hello again SCSI folks,
Attached are two patches for implementing the Specify Initiator Port Capable (SPEC_I_PT=1)
feature bit for handling of fabric dependent TransportIDs with PROUT service action REGISTER.
This is done by walking the PROUT parameter list, and calling fabric module dependent code for
extracting the TransportIDs and lengths, and then doing a second loop performing atomic adding
of pre-registered registrations for the fabric Initiator Ports referenced by TransportIDs.
This has been been tested with TCM/IBLOCK with fabric LIO-Target ports on v2.6.31-rc5 x86
32-bit KVM, please have a look at Patch 1 for an example using sg_persist + SPEC_I_PT=1 with
this code.
--nab
[PATCH 1/2] [Target_Core_Mod/Persistent_Reservations]: Add Specify Initiator Port Capable (SPEC_I_PT=1) support
[PATCH 2/2] [LIO-Target]: Update iSCSI TransportID parser to return length
drivers/lio-core/iscsi_target_tpg.c | 26 ++-
drivers/lio-core/iscsi_target_tpg.h | 2 +-
drivers/target/target_core_pr.c | 445 +++++++++++++++++++++++++++++--
include/target/target_core_fabric_ops.h | 2 +-
4 files changed, 448 insertions(+), 27 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists