From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Bart Van Assche <bart.vanassche@gmail.com>,
FUJITA Tomonori <tomof@acm.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, scst-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: SCSI target subsystem
Date: Sun, 04 May 2008 15:35:51 +0400 [thread overview]
Message-ID: <481D9F97.5090505@vlnb.net> (raw)
In-Reply-To: <20080503095314.GX14976@parisc-linux.org>
Matthew Wilcox wrote:
> On Sat, May 03, 2008 at 11:41:41AM +0200, Bart Van Assche wrote:
>> On Fri, May 2, 2008 at 8:17 PM, Vladislav Bolkhovitin <vst@vlnb.net> wrote:
>>> I wrote all above to support my at first glance shocking conclusion that
>>> SCSI target subsystem is completely new subsystem of the kernel and it
>>> should live on its own with its own maintainer! This is the same as with the
>>> current interaction between SCSI and block subsystems in the kernel: SCSI
>>> uses block's functionality, but that doesn't mean that block and SCSI are
>>> the same subsystem.
>> Hello Tomo,
>>
>> Due to the IET and STGT projects you have a lot of experience with
>> implementing SCSI target frameworks. What is your opinion about how a
>> kernel space SCSI target framework should fit in the Linux kernel ?
>
> Bart, what is your role in the SCST project? You don't seem to have
> contributed any code to it (going by the SVN logs on sourceforge), and
> your questions and suggestions seem to be those of someone not familiar
> with the code. If you're not a developer, it might be more helpful for
> you to step back and let Vladislav handle this.
Consider Bart as a member of SCST team at the moment responsible for
Linux kernel inclusion.
Vlad
next prev parent reply other threads:[~2008-05-04 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200805021638.42972.bart.vanassche@gmail.com>
[not found] ` <20080502153306.GB7376@infradead.org>
[not found] ` <e2e108260805020853r4c21fb98y3d4434a7fc95989c@mail.gmail.com>
[not found] ` <20080502155525.GA16353@infradead.org>
[not found] ` <e2e108260805020906w7f5e92bev46b8d0f96aa7b4d6@mail.gmail.com>
[not found] ` <1209745084.3121.39.camel@localhost.localdomain>
2008-05-02 18:09 ` [PATCH 2.6.25.1] Add scsi_execute_async_fifo() Vladislav Bolkhovitin
2008-05-02 18:17 ` SCSI target subsystem Vladislav Bolkhovitin
2008-05-03 9:41 ` Bart Van Assche
2008-05-03 9:53 ` Matthew Wilcox
2008-05-03 10:39 ` Bart Van Assche
2008-05-03 13:28 ` Matthew Wilcox
2008-05-03 14:48 ` Bart Van Assche
2008-05-04 15:53 ` Bart Van Assche
2008-05-04 11:35 ` Vladislav Bolkhovitin [this message]
2008-05-04 15:23 ` Vladislav Bolkhovitin
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=481D9F97.5090505@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bart.vanassche@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=scst-devel@lists.sourceforge.net \
--cc=tomof@acm.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