From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <tj@kernel.org>
Cc: maksim.rayskiy@gmail.com, linux-scsi@vger.kernel.org
Subject: Re: [RFC/PATCH] Deferred disk spinup during system resume
Date: Thu, 13 Jan 2011 12:20:00 -0500 [thread overview]
Message-ID: <4D2F3440.30701@pobox.com> (raw)
In-Reply-To: <20110113153707.GB12596@htj.dyndns.org>
On 01/13/2011 10:37 AM, Tejun Heo wrote:
> Hey, Jeff.
>
> On Wed, Jan 12, 2011 at 01:35:07PM -0500, Jeff Garzik wrote:
>> The previous patch breaks READ VERIFY translation for all cases
>> -except- this one.
>
> Ooh, right; then, can we just fix that?
>
>> The bottom line is that this patch simply wants to trigger an ATA
>> command, and return immediately, discarding the command results.
>> I'm not even sure a "run this command in background, and discard
>> results" facility requires the EH.
>
> It doens't necessarily require EH but the dependency is rather
> delicate because we still ride on SCSI EH. For example, we don't have
> any provision for running qc's without the associated scmd. If the
> command fails, libata EH rides on SCSI EH and the interaction relies
> on the association between qc's and scmd's. We may be able to add
> privison for this case but we already have working mechanism in EH for
> internal commands so it's just easiser that way.
In this case we -do- have an associated scmd, otherwise he would not be
able to trigger the READ VERIFY translation code.
So it seems a question of (a) who generates READ VERIFY, and (b) can we
have them issue the command without waiting for the results?
Which is something I would have thought SG_IO/bsg already provided...
It remains unclear to me why EH must be updated, simply to execute a
non-data ATA command without waiting.
Jeff
next prev parent reply other threads:[~2011-01-13 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 1:24 [RFC/PATCH] Deferred disk spinup during system resume maksim.rayskiy
2011-01-12 11:21 ` Tejun Heo
2011-01-12 18:35 ` Jeff Garzik
2011-01-12 20:01 ` Maksim Rayskiy
2011-01-13 15:39 ` Tejun Heo
2011-01-19 7:05 ` Jeff Garzik
2011-01-19 20:29 ` Maksim Rayskiy
2011-01-20 6:01 ` Jeff Garzik
2011-01-13 15:37 ` Tejun Heo
2011-01-13 17:20 ` Jeff Garzik [this message]
2011-01-13 17:24 ` 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=4D2F3440.30701@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-scsi@vger.kernel.org \
--cc=maksim.rayskiy@gmail.com \
--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 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.