From: Douglas Gilbert <dougg@torque.net>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI reserve / release support for SG
Date: Fri, 14 Nov 2003 22:19:40 +1000 [thread overview]
Message-ID: <3FB4C85C.9020907@torque.net> (raw)
In-Reply-To: <3FB4BC92.D43703BE@in.ibm.com>
Sachin Sant wrote:
> Does Current sg driver offer SCSI reserve/release command in its
> open/close function.
No.
> I am trying to run on a SAN or Cluster environment
> which requires support for this reserve/release command.
BTW www.t10.org traffic suggests more sophisticated reserve/
release mechanisms are in the pipeline. IOWs a solution to
your problem now could be an impediment a few years down the
track.
> If not then are there any plans to support reserve/release SCSI command
> so that sg driver can provide these options for its users in its
> open/close function It will make all I/O operation with sg driver more
> reliable especially in data storage area.
I'm getting this request from several angles. As someone
wryly pointed out ... as if we haven't got enough trouble
at the moment with the scsi subsystem implicitly issuing
scsi commands :-)
Seriously, I don't think issuing reserve/release SCSI commands
on the open and close of a pass-through interface is a good
idea. At a stretch it could be a non-default parameter on the
sg driver [lk 2.4 via /proc/scsi/sg; in lk 2.6 ...]
Just thinking about the implementation: currently sg will hold
its data structures alive if an unexpected close (e.g. user
control-C) occurs while a SCSI command is in flight. I guess
the point of what you are suggesting is to issue another scsi
command (i.e. release) in such a situation (and wait for
it (potentially as well as a command in progress)).
Doug Gilbert
next prev parent reply other threads:[~2003-11-14 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 11:29 SCSI reserve / release support for SG Sachin Sant
2003-11-14 12:19 ` Douglas Gilbert [this message]
2003-11-14 17:05 ` Mike Anderson
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=3FB4C85C.9020907@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=sachinp@in.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).