From: Tejun Heo <tj@kernel.org>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: JiSheng Zhang <jszhang3@gmail.com>,
Robert Hancock <hancockrwd@gmail.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Do we need to implement sr START/STOP management
Date: Thu, 3 Nov 2011 14:04:33 -0700 [thread overview]
Message-ID: <20111103210433.GL4417@google.com> (raw)
In-Reply-To: <4EB2CBAC.70003@interlog.com>
Hello,
On Thu, Nov 03, 2011 at 01:13:16PM -0400, Douglas Gilbert wrote:
> Do you mean the GET EVENT STATUS NOTIFICATION command (as there is
> no CHECK MEDIA EVENT STATUS command in SCSI or ATA)? If so it is
> one of the "good guys" along with the REQUEST SENSE command. And
> as I said TUR is not recommended. So looking at MS usage _and_
> the standards is a useful guide.
Yes, that's the one. Sorry, I always get confused about its name.
IIRC, it's a relatively new command, right? Anyways, I'm not arguing
standards are useless but that actual usages have to take precedence.
> I agree. SCSI and ATA define idle states (with some fuzziness in
> the naming) that have timers associated with them. Those
> mechanisms seem to work pretty well without the intervention of
> commands like START STOP UNIT.
Cool, thanks.
--
tejun
prev parent reply other threads:[~2011-11-03 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 5:31 Do we need to implement sr START/STOP management JiSheng Zhang
2011-11-01 5:53 ` James Bottomley
2011-11-01 6:35 ` JiSheng Zhang
2011-11-01 12:35 ` James Bottomley
2011-11-02 1:13 ` Robert Hancock
2011-11-03 6:38 ` JiSheng Zhang
2011-11-03 14:38 ` Tejun Heo
2011-11-03 15:34 ` Douglas Gilbert
2011-11-03 15:46 ` Tejun Heo
2011-11-03 17:13 ` Douglas Gilbert
2011-11-03 21:04 ` Tejun Heo [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=20111103210433.GL4417@google.com \
--to=tj@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dgilbert@interlog.com \
--cc=hancockrwd@gmail.com \
--cc=jszhang3@gmail.com \
--cc=linux-ide@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 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.