mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: michaelc@cs.wisc.edu, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, hch@lst.de,
	James.Bottomley@suse.de, hare@suse.de
Subject: Re: Conversion of LIO-Target to use include/scsi/iscsi_proto.h defs
Date: Fri, 20 Aug 2010 03:57:26 -0700	[thread overview]
Message-ID: <1282301846.30453.383.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20100820194231R.fujita.tomonori@lab.ntt.co.jp>

On Fri, 2010-08-20 at 19:43 +0900, FUJITA Tomonori wrote:
> On Fri, 20 Aug 2010 03:02:40 -0700
> "Nicholas A. Bellinger" <nab@linux-iscsi.org> wrote:
> 
> > review of TCM core and TCM_Loop.   But perhaps at this point LIO-Target
> > should go in together with TCM Core and TCM_Loop once mnc can review the
> > software iSCSI target pieces..?
> 
> I think that James meant that we have only one scsi target
> implementation and we need to replace the current in-kernel target
> mode driver. So I don't think that we can merge TCM core without its
> ibm vscsi driver. I might be wrong though.

Ah yes the ibm vscsi driver.   Well for that part I suppose we will need
a seperate tcm_ibmvscsi fabric module moving forward.  This is where
that python script I mentioned when tcm_lpfc, tcm_qla2xxx, tcm_mvsas
where originally posted that would generates a new functioning configfs
skeleton with NOP I/O path handlers from a handful of user input.

Anyways, something like this would really come in handy for making ibm
vscsi go, and plus it makes life easier for me too.  I will try to get a
script along this lines coded up in the next week(s) so that we can
finally have a pain-free method of generation for new v4 kernel target
mode modules for new developers.

There will be no limit per customer.  ;)

--nab


  reply	other threads:[~2010-08-20 11:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 22:45 Nicholas A. Bellinger
2010-08-20  7:32 ` FUJITA Tomonori
2010-08-20  9:14   ` Nicholas A. Bellinger
2010-08-20  9:41     ` FUJITA Tomonori
2010-08-20 10:02       ` Nicholas A. Bellinger
2010-08-20 10:43         ` FUJITA Tomonori
2010-08-20 10:57           ` Nicholas A. Bellinger [this message]
2010-08-20 21:41   ` Mike Christie
2010-08-20 23:55     ` Nicholas A. Bellinger
2010-08-22 19:06 ` Boaz Harrosh
2010-08-23 19:52   ` 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=1282301846.30453.383.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@suse.de \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --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 \
    /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®