From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [ANNOUNCE] Generic SCSI Target Middle Level for Linux (SCST) with target drivers
Date: Thu, 17 Jun 2004 17:22:12 +0400 [thread overview]
Message-ID: <40D19B04.40702@vlnb.net> (raw)
In-Reply-To: <20040617122213.GA30943@infradead.org>
Christoph Hellwig wrote:
> On Wed, Jun 16, 2004 at 08:31:22PM +0400, Vladislav Bolkhovitin wrote:
>
> The code looks pretty neat to me, there's a few issues I'd like to see
> addresses but that doesn't make sense before the 2.4 support is dropped
> and there's an actual LLDD for 2.6. But I think for most interesting
> scenarios in the storage virtualization world your driver is pretty much
> useless because it wants to dispatch directly to a scsi device and doesn't
> go through the block layer. So no fancy volume managers/etc there to make
> interesting storage virtualization boxes.
>
For that is intended upcoming block device handler with block
layer/cache support,
which will be in its exec() method check, if requested blocks in cache,
and, if not, dispatch the commands to block layer, leaving regular
scsi_do_req() calls for tapes, changers, etc. In the similar way "_perf"
handlers work (they don't send READ/WRITE commands to SCSI devices for
performance studies).
This device handler is on our todo list. Actually, it's quite simple and
if anyone interested, he's help would be greatly appreciated.
Thanks,
Vlad
prev parent reply other threads:[~2004-06-17 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 16:31 [ANNOUNCE] Generic SCSI Target Middle Level for Linux (SCST) with target drivers Vladislav Bolkhovitin
2004-06-16 18:21 ` Matthew Wilcox
2004-06-17 12:15 ` Vladislav Bolkhovitin
2004-06-17 12:22 ` Christoph Hellwig
2004-06-17 13:22 ` Vladislav Bolkhovitin [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=40D19B04.40702@vlnb.net \
--to=vst@vlnb.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox