mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: linux-scsi <linux-scsi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Hannes Reinecke <hare@suse.de>,
	James Bottomley <James.Bottomley@suse.de>,
	Jens Axboe <axboe@kernel.dk>,
	Richard Sharpe <realrichardsharpe@gmail.com>,
	Joel Becker <joel.becker@oracle.com>
Subject: Re: tcm: Add Documentation/target/tcm_mod_builder.py script and mini-HOWTO
Date: Tue, 24 Aug 2010 16:14:42 -0700	[thread overview]
Message-ID: <1282691682.32007.71.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1282683207.32007.40.camel@haakon2.linux-iscsi.org>

On Tue, 2010-08-24 at 13:53 -0700, Nicholas A. Bellinger wrote:
> Greetings all,
> 
> The initial commit for the new tcm_mod_builder.py script has been pushed
> into lio-core-2.6.git/lio-4.0!  Included is a brief mini-HOWTO as to how
> the TCM fabric module generation logic actually functions, and what is
> currently supported.  I thought instead of spamming the kernel lists
> with 1K LOC of python for actually generating *new* TCM kernel fabric
> modules, it might be easier to post the HOWTO to the list and a gitweb
> URL of the script itself for those interested parties here:
> 
> http://www.kernel.org/pub/linux/kernel/people/nab/Documentation/target/tcm_mod_builder.py
> 
> So after a single day of python coding things are working remarkably
> well, so far I am able to generate functioning ConfigFS skeletons with
> proper target_core_fabric_lib.c Transport / WWPN handlers, eg:
> multi-fabric transitional SPC-3 PR and ALUA (configfs attributes
> included) that work right out of the box.
> 
> There are are a list of remaining TODO items at the bottom of the doc,
> but I hope that people will actually give this script a shot and see for
> themselves how easy the generation of new configfs code for TCM fabric
> modules can really be!
> 
> Comments are welcome, Enjoy!
> 

Just a quick followup, the functional kernel source generated by the
tcm_mod_builder.py mini-HOWTO example can be found here:

http://www.kernel.org/pub/linux/kernel/people/nab/tcm_nab5000/

This example is currently using 'main():proto_ident=iSCSI' to generate
iSCSI specific structure member naming, and includes the necessary
$PROTO_IDENT dependent code from drivers/target/target_core_fabric_lib.c
into the newly generated TCM fabric module in order to provide a running
TransportID / WWPN model in ConfigFS for high level logic from
drivers/target/target_core_pr.c and friends to 'just work'.

Comments are welcome, thanks!

--nab



      reply	other threads:[~2010-08-24 23:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 20:53 Nicholas A. Bellinger
2010-08-24 23:14 ` 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=1282691682.32007.71.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@suse.de \
    --cc=axboe@kernel.dk \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=joel.becker@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=realrichardsharpe@gmail.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®