From: Todd E Brandt <todd.e.brandt@linux.intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com, rjw@rjwysocki.net
Subject: Re: [PATCH/RESEND v2 1/2] Hard disk S3 resume time optimization
Date: Mon, 13 Jan 2014 15:30:26 -0800 [thread overview]
Message-ID: <20140113233026.GA3200@linux.intel.com> (raw)
In-Reply-To: <20140113203007.GA3480@mtj.dyndns.org>
On Mon, Jan 13, 2014 at 03:30:07PM -0500, Tejun Heo wrote:
> Hello,
>
> On Mon, Jan 13, 2014 at 11:55:44AM -0800, Todd E Brandt wrote:
> > I see your point, why have two paths if one will do. The only thing that
> > worries me is that the PM resume from hibernate function doesn't have
> > an error handler. What happens when it tries to read the image from swap
> > and the disk is still spinning up? The scsi layer has an error handler so
>
> The request gets blocked on EH.
>
> > it just keeps retrying every few seconds, but the PM core reads directly
> > from the swap disk's block device.
>
> Why would that matter? Resume is handled by EH. While EH is in
> progress, all commands are blocked. Am I missing something?
No, I am. You're right, there shouldn't be an issue. I'm just sketchy about
new changes that I haven't tested. Lemme code up the change and do some
stress testing to be sure there are no issues.
>
> > > So, can't just everything become async? Are there cases where we
> > > *need* synchronous PM behaviors?
> >
> > I think suspend still needs to be synchronous, because the PM core needs
> > to be sure that the disks are actually spun down before it can attempt
> > to shut the system down. I'm adding Raphael to the thread. Raphael, is
> > this correct?
>
> Yeah, we definitely should wait for suspend to complete before
> entering suspend state. I was referring to the resume path.
Ahh, sorry, yea I think async should work for the entire resume pathway. Would
you be willing to accept this ata patch separately from the scsi one? It
wouldn't provide any performance benefit on its own, but would pave the way
for performance benefit by removing the ATA resume lag time (Which would then
put the ball in the scsi layer's court to finish the optimization). I've
tested both patches separately and both work without issue. Also, this patch
appears to be a pre-requisite to both mine and Phillip Susi's solution, so
it would really hope move things along regardless of which direction is
ultimately chosen in the SCSI layer.
>
> Thanks.
>
> --
> tejun
next prev parent reply other threads:[~2014-01-13 23:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 0:56 [PATCH/RESEND v2 1/2] Hard disk S3 resume time optimization Todd E Brandt
2014-01-09 17:03 ` Phillip Susi
2014-01-10 23:11 ` Brandt, Todd E
2014-01-11 2:13 ` Phillip Susi
2014-01-11 3:13 ` Dan Williams
2014-01-13 20:06 ` Todd E Brandt
2014-01-13 20:37 ` Dan Williams
2014-01-13 23:51 ` Todd E Brandt
2014-01-14 0:05 ` Dan Williams
2014-01-11 19:13 ` Tejun Heo
2014-01-13 19:55 ` Todd E Brandt
2014-01-13 20:30 ` Tejun Heo
2014-01-13 23:30 ` Todd E Brandt [this message]
2014-01-14 14:31 ` Tejun Heo
2014-01-15 0:31 ` [PATCH v3 0/2] " Todd E Brandt
2014-01-15 12:55 ` Tejun Heo
2014-01-15 0:31 ` [PATCH v3 1/2] " Todd E Brandt
2014-01-15 13:01 ` Tejun Heo
2014-01-15 20:04 ` Todd E Brandt
2014-01-15 0:32 ` [PATCH v3 2/2] " Todd E Brandt
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=20140113233026.GA3200@linux.intel.com \
--to=todd.e.brandt@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).