mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <greg@kroah.com>, Douglas Gilbert <dgilbert@interlog.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Hannes Reinecke <hare@suse.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Joel Becker <joel.becker@oracle.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Florian Haas <florian.haas@linbit.com>,
	Philipp Reisner <philipp.reisner@linbit.com>
Subject: Re: [RFC PATCH 0/19] A kernel-level configfs enabled generic target engine for Linux v2.6.32
Date: Mon, 14 Sep 2009 12:59:54 -0700	[thread overview]
Message-ID: <1252958394.2067.277.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <4AACC4FD.8050402@panasas.com>

On Sun, 2009-09-13 at 13:10 +0300, Boaz Harrosh wrote:
> On 09/12/2009 04:55 AM, Nicholas A. Bellinger wrote:
> > Greetings all,
> > 
> > This is my humble request for review and inclusion of
> > Target_Core_Mod/ConfigFS v3.2 from lio-core-2.6.git code into mainline
> > v2.6.32.  With TCM v3.2, the two major SPC-4 SCSI target mode fabric
> > features that have now been completed: Persistent Reservation APTPL and
> > implict/explict ALUA are the first all optional SPC4 defined feature
> > implementation of PR and ALUA in the Linux OSS target theatre using an
> > upstream user-driven virtual filesystem directory hierarchy structure
> > based on configfs that can be configured in realtime in combination with
> > interpreted userspace code.
> > 
> > Both of these new features are now being used to provide Persistent Reservations
> > across target power loss and asymmetric multipath I/O to both Linux and non-Linux
> > clients.  There is also an optional ALUA transition delay logic that has been
> > included to futher debug and improve existing upstream client side Linux kernel code
> > using TCM v3.2. These patches have been diffed against v2.6.31, and tested on x86
> > 32-bit HVM, x86_64 KVM, and powerpc.
> > 
> > There is cleanup work continuing to make the TCM code to use dprintk(),
> > and some include cleanups, and other minor fixes.  The code has also
> > been run through checkpatch again since the posting in April, and all
> > errors have been removed, with the exception of one ConfigFS macro
> > define triggering a checkpatch false positive.
> > 
> > As with the posting of the TCM v3.0 code earlier in April, I have
> > decided to break up the submissions into the generic target_core_mod
> > piece (this patch series) and then a seperate one that will be appearing
> > in the next days for v3.2 of the LIO-Target iSCSI fabric module.
> > 
> > More Information about Target_Core_Mod/ConfigFS, and PR and ALUA:
> > 
> > http://www.linux-iscsi.org/index.php/Target_Core_Mod/ConfigFS
> > http://www.linux-iscsi.org/index.php/Persistent_Reservations
> > http://www.linux-iscsi.org/index.php/ALUA
> > 
> > The complete v3.x TCM CLI operations set can be found here:
> > 
> > http://www.linux-iscsi.org/index.php/Lio-utils#v3.1_TCM_CLI_operations
> > 
> > Instructions and examples for getting setup:
> > 
> > http://linux-iscsi.org/builds/docs/LIO-3.0-Users_Reference_Manual.pdf
> > http://www.linux-iscsi.org/index.php/Howto#Start_target_core_mod
> > 
> > Constructive comments are welcome,
> > 
> > --nab
> > 
> > ==> target_core_alua.patch <==
> > [RFC PATCH 1/19] Target_Core_Mod Asymmetric Logical Unit Assignment (ALUA) support
> > ==> target_core_configfs.patch <==
> > [RFC PATCH 2/19] Target_Core_Mod ConfigFS infrastructure
> > ==> target_core_device.patch <==
> > [RFC PATCH 3/19] Target_Core_Mod device core infrastructure
> > ==> target_core_file.patch <==
> > [RFC PATCH 4/19] Target_Core_Mod FILEIO <-> Linux/VFS subsystem
> > ==> target_core_hba.patch <==
> > [RFC PATCH 5/19] Target_Core_Mod HBA core infrastructure
> > ==> target_core_iblock.patch <==
> > [RFC PATCH 6/19] Target_Core_Mod IBLOCK <-> Linux/Block subsystem plugin
> > ==> target_core_mib.patch <==
> > [RFC PATCH 7/19] Target_Core_Mod SCSI MIBs
> > ==> target_core_plugin.patch <==
> > [RFC PATCH 8/19] Target_Core_Mod Subsystem and SE Object plugin infrastructure
> > ==> target_core_pr.patch <==
> > [RFC PATCH 9/19] Target_Core_Mod SPC-4 Persistent Reservations
> > ==> target_core_pscsi.patch <==
> > [RFC PATCH 10/19] Target_Core_Mod PSCSI <-> Linux/SCSI subsystem plugin
> > ==> target_core_rd.patch <==
> > [RFC PATCH 11/19] Target_Core_Mod RAMDISK_DR and RAMDISK_MCP subsystem plugin
> > ==> target_core_scdb.patch <==
> > [RFC PATCH 12/19] Target_Core_Mod READ/WRITE command descriptor block generation code
> > ==> target_core_seobj.patch <==
> > [RFC PATCH 13/19] Target_Core_Mod Storage Engine Object infrastructure
> > ==> target_core_tmr.patch <==
> > [RFC PATCH 14/19] Target_Core_Mod Task Management infrastructure
> > ==> target_core_tpg.patch <==
> > [RFC PATCH 15/19] Target_Core_Mod portal group endpoint infrastructure
> > ==> target_core_transport.patch <==
> > [RFC PATCH 16/19] Target_Core_Mod Generic Transport Core
> > ==> target_core_ua.patch <==
> > [RFC PATCH 17/19] Target_Core_Mod Unit Attention emulation support
> > ==> target_core_base_includes.patch <==
> > [RFC PATCH 18/19] Target_Core_Mod base and fabric_module includes
> > ==> target_core_misc.patch <==
> > [RFC PATCH 19/19] Target_Core_Mod Makefile/Kconfig and div64.c
> > 
> 
> I would like to see a documentation patch which adds a file under Documentation/
> With some abstraction, design, usability, URLs
> 
> I promise to read it ;-)
> 
> I'm sure you have lots of stuff written laying around. Could you edit them up for
> Linux?

Understood, I will put together something for Documentation/ and include
it in the next round of patches.

Many thanks for your most valuable of time,

--nab

> 
> Boaz



  reply	other threads:[~2009-09-14 20:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-12  1:55 Nicholas A. Bellinger
2009-09-12  2:37 ` Daniel Walker
2009-09-12  3:08   ` Nicholas A. Bellinger
2009-09-12  3:17     ` Daniel Walker
2009-09-12  3:24       ` Nicholas A. Bellinger
2009-09-13 10:10 ` Boaz Harrosh
2009-09-14 19:59   ` Nicholas A. Bellinger [this message]
2009-09-14 18:50 ` Vladislav Bolkhovitin
2009-09-14 20:49   ` Nicholas A. Bellinger
2009-09-15 18:08     ` Vladislav Bolkhovitin
2009-09-14 20:12 ` Chetan.Loke
2009-09-14 21:06   ` Nicholas A. Bellinger

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=1252958394.2067.277.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharrosh@panasas.com \
    --cc=dgilbert@interlog.com \
    --cc=florian.haas@linbit.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=greg@kroah.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=joel.becker@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michaelc@cs.wisc.edu \
    --cc=philipp.reisner@linbit.com \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®