From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Tejun Heo <tj@kernel.org>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
michaelc@cs.wisc.edu, hch@lst.de, hare@suse.de,
James.Bottomley@suse.de, axboe@kernel.dk, bharrosh@panasas.com,
jeff@garzik.org
Subject: Re: [RFC v2 00/21] TCM Core and TCM_Loop patches for v2.6.37
Date: Wed, 06 Oct 2010 21:13:58 +0400 [thread overview]
Message-ID: <4CACAE56.6090209@vlnb.net> (raw)
In-Reply-To: <4CAC833F.2010108@kernel.org>
Tejun Heo, on 10/06/2010 06:10 PM wrote:
> On 10/06/2010 09:24 AM, Nicholas A. Bellinger wrote:
>>> I like to hear the opinions of SCSI maintainer and ATA folks.
>>
>> jejb, jgarzik, tejun and co..? Any thoughts here..?
>
> I frankly have no idea whatsoever. Is there something I can read to
> educate myself on the subject?
General information about a SCSI target subsystem you can find in
http://scst.sourceforge.net. More internal details about implementation
in http://scst.sourceforge.net/scst_pg.html. Features which are
implemented in http://scst.sourceforge.net/comparison.html.
Directly on the subject you can find some considerations in
http://lkml.org/lkml/2010/10/1/140 (second half of the message).
My opinion is that in ideal the SCSI initiator subsystem should be
drivers/scsi/initiator and the target subsystem - drivers/scsi/target
with shared code in drivers/scsi/. But in reality such big
reorganization is unlikely possible, so it's better to leave SCSI
initiator subsystem in drivers/scsi and the target subsystem - in the
separate directory in drivers/ (drivers/scst for SCST).
Vlad
next prev parent reply other threads:[~2010-10-06 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 22:48 [RFC v2 00/21] TCM Core and TCM_Loop patches for v2.6.37 Nicholas A. Bellinger
2010-10-06 2:21 ` FUJITA Tomonori
2010-10-06 4:46 ` Nicholas A. Bellinger
2010-10-06 7:09 ` FUJITA Tomonori
2010-10-06 7:24 ` Nicholas A. Bellinger
2010-10-06 14:10 ` Tejun Heo
2010-10-06 17:13 ` Vladislav Bolkhovitin [this message]
2010-10-11 14:18 ` Tejun Heo
2010-10-11 20:26 ` 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=4CACAE56.6090209@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@suse.de \
--cc=axboe@kernel.dk \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.