linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Tejun Heo <tj@kernel.org>
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, 03 Nov 2011 13:13:16 -0400	[thread overview]
Message-ID: <4EB2CBAC.70003@interlog.com> (raw)
In-Reply-To: <CAOS58YM2rwwaqEBDEHdBy_Mo_3FJsJUsHmdBM=T4hyApmKuOuA@mail.gmail.com>

On 11-11-03 11:46 AM, Tejun Heo wrote:
> On Thu, Nov 3, 2011 at 8:34 AM, Douglas Gilbert<dgilbert@interlog.com>  wrote:
>> That's a pretty poor attitude. I suspect Microsoft care. If so they
>> would be transitioning away from TEST UNIT READY to REQUEST SENSE
>> to monitor power conditions and the progress indication.
>
> I was talking about media presence polling.  We used to include TUR in
> the sequence and there have been some number of devices which worked
> fine for a while but lock up eventually.  Windows only issues
> CHECK_MEDIA_EVENT_STATUS so nobody has tested extended TUR cycles and

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.


BTW The REQUEST SENSE implemented in the libata's SAT layer is
completely broken (and has been since day one). Is anyone planning
to fix it? An LSI SAS HBA with recent firmware and accessing a
SATA disk is a pretty good example of what a compliant SAT layer
looks like.

> nobody is fixing an optical drive EOL'd six months ago either, so what
> I or you think or feel doesn't matter in the end.  The most important
> thing is we provide drivers which allow proper operation and, sadly,
> at this point, the best way to get there is following what windows
> does.  It's not like we lose any functionality that way anyway.
>
> If windows isn't spinning down the drive, it is highly unlikely that
> missing that harms anything and it's highly like there are a bunch of
> devices which would go "uh... what the hell is this? I don't know
> this. osidfjalekjalkgjs".  So, there simply is no point at all.

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.

Doug Gilbert


  reply	other threads:[~2011-11-03 17:13 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 [this message]
2011-11-03 21:04                 ` Tejun Heo

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=4EB2CBAC.70003@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=hancockrwd@gmail.com \
    --cc=jszhang3@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).