mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: LKML <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Cc: Douglas Gilbert <dgilbert@interlog.com>,
	Hannes Reinecke <hare@suse.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Mike Christie <michaelc@cs.wisc.edu>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	James Smart <James.Smart@Emulex.Com>,
	Philipp Reisner <philipp.reisner@linbit.com>
Subject: [PATCH 0/2] [Target_Core_Mod/Persistent_Reservations]: Add SPEC_I_PT=1 support
Date: Sat, 08 Aug 2009 21:56:02 -0700	[thread overview]
Message-ID: <1249793762.11105.233.camel@haakon2.linux-iscsi.org> (raw)

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(-)



                 reply	other threads:[~2009-08-09  5:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1249793762.11105.233.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=James.Smart@Emulex.Com \
    --cc=akpm@linux-foundation.org \
    --cc=dgilbert@interlog.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=philipp.reisner@linbit.com \
    /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

all inboxes | Powered by JetHome®