From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: SCSI API generics (was Re: [PATCH] add block/unblock to iscsi class)
Date: Wed, 23 Feb 2005 10:17:05 -0800 [thread overview]
Message-ID: <20050223181705.GA8694@plap.qlogic.org> (raw)
In-Reply-To: <421C3CA4.8070009@cs.wisc.edu>
On Wed, 23 Feb 2005, Mike Christie wrote:
> The attached patch copies the code from the fc transport
> class which allows a LLD to block and unblock a device.
> The block/unblock code is used by the iscsi-sfnet
> driver in replacement of a internal timer doing the
> same thing.
>
> I understand that the target code is under construction
> and our group as well as the HW iSCSI guys are trying to move
> to something closer to the fc's rport model, so I was not
> sure if it is better to wait or get this basic functionality in
> first so we (and other SW and HW iSCSI drivers) can kill some
> of our duplicated code sooner and then incrementally update
> the class.
>
Speaking of which, are there any major objections to the patches
proposed here:
Add scsi_target_[un]block() and scsi_target_remove() generics
http://marc.theaimsgroup.com/?l=linux-scsi&m=110867050306738&w=2
[RFC] adding per scsi-host workqueues for defered processing
http://marc.theaimsgroup.com/?l=linux-scsi&m=110903148407438&w=2
which add some infrastructure changes for the transport classes.
--
AV
next prev parent reply other threads:[~2005-02-23 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 8:19 [PATCH] add block/unblock to iscsi class Mike Christie
2005-02-23 18:17 ` Andrew Vasquez [this message]
2005-02-23 19:55 ` SCSI API generics (was Re: [PATCH] add block/unblock to iscsi class) Mike Christie
2005-02-23 22:06 ` Andrew Vasquez
2005-02-24 0:00 ` Mike Christie
2005-02-24 0:03 ` Mike Christie
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=20050223181705.GA8694@plap.qlogic.org \
--to=andrew.vasquez@qlogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox