From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Chetan.Loke@Emulex.Com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
akpm@linux-foundation.org, greg@kroah.com, dgilbert@interlog.com,
James.Bottomley@HansenPartnership.com, hare@suse.de,
fujita.tomonori@lab.ntt.co.jp, michaelc@cs.wisc.edu,
joel.becker@oracle.com, martin.petersen@oracle.com, hch@lst.de,
torvalds@linux-foundation.org, stern@rowland.harvard.edu,
bharrosh@panasas.com, florian.haas@linbit.com,
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 14:06:35 -0700 [thread overview]
Message-ID: <1252962395.2067.325.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <412A05BA40734D4887DBC67661F4330810060F29@EXMAIL.ad.emulex.com>
On Mon, 2009-09-14 at 13:12 -0700, Chetan.Loke@Emulex.Com wrote:
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> > owner@vger.kernel.org] On Behalf Of Nicholas A. Bellinger
> > Sent: Friday, September 11, 2009 9:55 PM
> > To: LKML; linux-scsi
> > Cc: Andrew Morton; Greg KH; Douglas Gilbert; James Bottomley; Hannes
> > Reinecke; FUJITA Tomonori; Mike Christie; Joel Becker; Martin K. Petersen;
> > Christoph Hellwig; Linus Torvalds; Alan Stern; Boaz Harrosh; Florian Haas;
> > Philipp Reisner
> > Subject: [RFC PATCH 0/19] A kernel-level configfs enabled generic target
> > engine for Linux v2.6.32
> >
> > 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
> >
>
>
>
> Any pointers/URLs for the design/arch doc?
Greetings Chetan,
There are various bits and pieces detailing the TCM design on the
linux-iscsi.org wiki, but no definitive design document (aside from the
comments in the code) is available yet.
I will however be putting together a first draft for this (along with
the user-level stuff) for Documentation/ soon. Until then, I would be
happy to answer any questions you may have.
--nab
>
>
> Chetan
prev parent reply other threads:[~2009-09-14 21:06 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
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 [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=1252962395.2067.325.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=Chetan.Loke@Emulex.Com \
--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®