From: Vladislav Bolkhovitin <vst@vlnb.net>
To: linux-scsi@vger.kernel.org
Cc: James.Smart@Emulex.Com
Subject: Re: [PATCH 3/3] MidLayer updates - extending scsi_target support
Date: Sun, 06 Feb 2005 17:18:19 +0300 [thread overview]
Message-ID: <4206272B.6030106@vlnb.net> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12EAB3@xbl3.ma.emulex.com>
Please, forgive me my ignorance, it looks like something was happened
"behind the scene" (linux-scsi list), and I missed it. Is support for
SCSI targets started to be added in Linux? I mean "SCSI targets" as the
ability to export local devices on a SCSI bus. If so, please consider
proposed SCSI target mid-level (SCST) living on
http://scst.sourceforge.net. In the next few weeks we are going to clean
it a bit and prepare the patch, so it could start being part of some
testing tree, probably "-mm", although it is stable enough ever for
Linus one.
BTW, are there any descriptions for current scsi_target support and in
which direction it's moving?
Vlad
James.Smart@Emulex.Com wrote:
> Patch 3:
> This patch extends scsi_target support:
> - Allows for driver-specific data to be allocated along with the
> target structure and accessible via the starget->hostdata pointer.
> - Adds scsi target alloc/configure/destory callbacks to the
> scsi host template.
> - Rearranges the calling sequences for scsi targets so that the
> target and slave alloc/configure/destory callbacks are in
> order (target before slave on alloc/configure).
>
> -- James S
next prev parent reply other threads:[~2005-02-06 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 14:03 [PATCH 3/3] MidLayer updates - extending scsi_target support James.Smart
2005-02-04 23:00 ` James Bottomley
2005-02-06 14:18 ` Vladislav Bolkhovitin [this message]
2005-05-24 17:06 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-02-05 15:04 James.Smart
2005-02-06 1:44 ` Douglas Gilbert
2005-02-06 2:00 James.Smart
2005-02-06 17:28 James.Smart
2005-02-06 17:33 ` Christoph Hellwig
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=4206272B.6030106@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Smart@Emulex.Com \
--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 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.