From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: lsf10-pc@lists.linuxfoundation.org
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [LSF/VM TOPIC] TCM v4.0 generic configfs fabric infrastructure
Date: Wed, 31 Mar 2010 23:23:34 -0700 [thread overview]
Message-ID: <1270103014.2682.58.camel@haakon2.linux-iscsi.org> (raw)
Greetings all,
[Topic]
TCM v4.0 generic configfs fabric infrastructure
[Abstract]
This discussion focuses on the generic configfs fabric module
infrastructure WIP currently under development for TCM v4.0 which aims
to provide a generic set of struct config_item_types available for
target mode fabric module configfs usage, and set of context specific
macros available for adding target mode fabric module dependent RW
configfs attributes. The main goal is to enable the development of new
and conversion of existing target mode fabric modules without the hard
requirement of fabric module authors needing to implement their own
configfs code.
The patch announcements for the first and second series of TCM code and
LIO-Target and TCM_Loop fabric module conversion commits into
lio-core-2.6.git/lio-4.0 can be found here:
http://marc.info/?l=linux-scsi&m=126688745100913&w=2
http://marc.info/?l=linux-scsi&m=126710672402056&w=2
and code for implementing the generic WWN, TPGT, LUN, NodeACL and
MappedLUN struct configs_item_types is available here:
http://git.kernel.org/?p=linux/kernel/git/nab/lio-core-2.6.git;a=blob;f=drivers/target/target_core_fabric_configfs.c;hb=lio-4.0
Best,
--nab
reply other threads:[~2010-04-01 6:23 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=1270103014.2682.58.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.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).