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: Hannes Reinecke <hare@suse.de>,
	Florian Haas <florian.haas@linbit.com>,
	Philipp Reisner <philipp.reisner@linbit.com>,
	Christoph Hellwig <hch@lst.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Richard Sharpe <realrichardsharpe@gmail.com>,
	Boaz Harrosh <bharrosh@panasas.com>,
	Daniel Walker <dwalker@fifo99.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Avi Kivity <avi@redhat.com>,
	Gregory Haskins <gregory.haskins@gmail.com>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: [ANNOUNCE] Initial release of tcm_loop.ko virtual SCSI fabric module TCM Core 3.2
Date: Tue, 20 Oct 2009 09:33:13 -0700	[thread overview]
Message-ID: <1256056393.4263.150.camel@haakon2.linux-iscsi.org> (raw)

Greetings all,

I am happy to announce the first release of the tcm_loop.ko virtual SCSI
fabric module for TCM Core v3.2 that provides CDB-level SPC-3 and above
emulation for SAS Target and Initiator Port Addresses.  This allows
virtual TCM storage objects like BLOCK, FILEIO and RAMDISK to be
presented as locally accessable Linux/SCSI devices (/dev/sdz) using CDB
level emulation capable of TCM/LIO v3.2 T10 NAA WWN naming, Persistent
Reservations, and ALUA logic.

So far, sg_persist is able to span reservations between multiple
emulated SAS I_T Nexues, as well as across iSCSI Target Ports for the
same TCM backend storage object.  Also, the ability to pass the locally
accessable TCM_Loop virtual SCSI luns using scsi_generic SG_IO
passthrough into VM guests of different operating systems (RHEL5 and
NetBSD5 for example) is also up and running on top of the vmw6
hypervisor mpt-fusion HBA emulation on a Linux v2.6.32-rc5 host.

For more information and screenshots, please see:

http://linux-iscsi.org/index.php/TCM_loop

Here is the original running commit for the kernel piece:

http://git.kernel.org/?p=linux/kernel/git/nab/lio-core-2.6.git;a=commitdiff;h=10eae38203a01a26fca3b2097f13e48a0ba2d38f

And the tcm_loop.py CLI commit:

http://git.kernel.org/?p=linux/storage/lio/lio-utils.git;a=commitdiff;h=564dcf1733bb8591f02900c644f0694e1fb2af35

There is still some of work to be done in tcm_loop_configfs.c, and the
struct scsi_host_template for the emulated SCSI LLD is pretty much just
queuecommand() and proc() currently, so it needs TMR LUN_RESET.  Also
can_queue needs to be ramped up to 32 and ENABLE_CLUSTERING set, and so
far the tcm_loop virtual SCSI LUNs are able to pass simple badblocks
tests, and able to push bulk I/O.

Thanks!

--nab






                 reply	other threads:[~2009-10-20 16:33 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=1256056393.4263.150.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=bharrosh@panasas.com \
    --cc=dwalker@fifo99.com \
    --cc=florian.haas@linbit.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=gregory.haskins@gmail.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=philipp.reisner@linbit.com \
    --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®