All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 20 Jan 2011 01:01:08 -0500	[thread overview]
Message-ID: <4D37CFA4.6030601@pobox.com> (raw)
In-Reply-To: <AANLkTikcrznVeySm42NDYtWtKJBypSXCRv1QsOBug5zQ@mail.gmail.com>

On 01/19/2011 03:29 PM, Maksim Rayskiy wrote:
>> 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
>>
>
> My question was how to speed up system resume when he the spinup
> request is coming from sd_resume(). For shell method to work I would
> have to ignore this request entirely and do READ VERIFY when system is
> fully restored.
> Can it be done without kernel modification? Tejun mentioned using
> manage_start_stop flag but had some reservations against it.

Oh, if we're talking about sd_resume(), SCSI definitely has an internal 
mechanism to fire off a request, without blocking and waiting for a 
response.  It does sound like a kernel modification, but it should be 
straightforward via existing APIs.

	Jeff




  reply	other threads:[~2011-01-20  6:01 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 [this message]
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=4D37CFA4.6030601@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 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.