From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: todd.e.brandt@linux.intel.com
Cc: JBottomley@parallels.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH/RESEND v2 1/2] Hard disk resume time optimization, asynchronous ata_port_resume
Date: Tue, 3 Dec 2013 16:35:58 +0000 [thread overview]
Message-ID: <20131203163558.354e2efd@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20131203162735.GB12554@linux.intel.com>
> thus allowing the UI to come online sooner. There may be a short period after
> resume where the disks are still spinning up in the background, but the user
> shouldn't notice since the OS can function with the data left in RAM.
I wonder how many marginal power supplies this will find 8)
I still think it's the right thing to do. In the SCSI world a bit more
caution was needed however.
Alan
prev parent reply other threads:[~2013-12-03 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 16:27 [PATCH/RESEND v2 1/2] Hard disk resume time optimization, asynchronous ata_port_resume Todd E Brandt
2013-12-03 16:35 ` One Thousand Gnomes [this message]
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=20131203163558.354e2efd@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=JBottomley@parallels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@kernel.org \
--cc=todd.e.brandt@linux.intel.com \
/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