From: Jeff Garzik <jgarzik@pobox.com>
To: Maksim Rayskiy <maksim.rayskiy@gmail.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-scsi@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [RFC/PATCH] Deferred disk spinup during system resume
Date: Wed, 19 Jan 2011 02:05:31 -0500 [thread overview]
Message-ID: <4D368D3B.7030701@pobox.com> (raw)
In-Reply-To: <AANLkTikEusD_CvkOERsr_wr7T70g1kuU=JnBJm5ur5Wg@mail.gmail.com>
On 01/12/2011 03:01 PM, Maksim Rayskiy wrote:
>>
>> 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.
>>
>
> This is why I was asking if using a workqueue instead of EH might be a
> better idea.
> EH looks like an overkill here.
A kernel modification might not even be needed.
Have you tried simply issuing READ VERIFY via bsg, and not caring if it
completes? bsg should be able to handle an app submitting a command,
but never checking the 'done' list, right? A simple shell app could execute
write(bsg_fd, ... SCSI READ VERIFY command ...)
exit(0)
to avoid waiting for READ VERIFY command completion, I would hope.
Jeff
next prev parent reply other threads:[~2011-01-19 7:05 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 [this message]
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=4D368D3B.7030701@pobox.com \
--to=jgarzik@pobox.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--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