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: Wed, 12 Jan 2011 13:35:07 -0500 [thread overview]
Message-ID: <4D2DF45B.5010101@pobox.com> (raw)
In-Reply-To: <20110112112142.GA9610@mtj.dyndns.org>
On 01/12/2011 06:21 AM, Tejun Heo wrote:
> Hello, Maksim, Jeff.
>
> On Tue, Jan 11, 2011 at 05:24:17PM -0800, maksim.rayskiy@gmail.com wrote:
>> @@ -4978,6 +4978,13 @@ void ata_qc_issue(struct ata_queued_cmd *qc)
>> struct ata_link *link = qc->dev->link;
>> u8 prot = qc->tf.protocol;
>>
>> + if (unlikely(qc->flags& ATA_QCFLAG_VERIFY)) {
>> + ata_port_schedule_eh(ap);
>> + qc->scsidone(qc->scsicmd);
>> + ata_qc_free(qc);
>> + return;
>
> I still prefer the original patch where EH is scheduled from the
> translation layer. This seems unnecessarily intrusive to me. As I
> wrote before, it's not like we have a clean translation anyway and I
> think this better fits as impedance matching code in the translation
> layer anyway. But, that said, this is a rather ugly piece of code
> which is necessary just to work around the fact that we live under
> scsi, so as long as it works, one way or the other probably doesn't
> matter all that much (the reason why I prefer the previous one, as it
> doens't try to be pretty and just gets it done), so it's Jeff's call.
The previous patch breaks READ VERIFY translation for all cases -except-
this one.
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.
Jeff
next prev parent reply other threads:[~2011-01-12 18:35 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 [this message]
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
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=4D2DF45B.5010101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox