From: Phillip Susi <psusi@ubuntu.com>
To: Todd Brandt <todd.e.brandt@linux.intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
tj@kernel.org, JBottomley@Parallels.com,
Len Brown <len.brown@intel.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH v5 2/3] libata: async resume
Date: Fri, 19 Dec 2014 18:46:25 -0500 [thread overview]
Message-ID: <5494B8D1.1070608@ubuntu.com> (raw)
In-Reply-To: <20140305201735.20088.22124.stgit@viggo.jf.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 03/05/2014 03:17 PM, Dan Williams wrote:
> From: Todd Brandt <todd.e.brandt@linux.intel.com>
>
> Improve overall system resume time by making libata link recovery
> actions asynchronous relative to other resume events.
>
> Link resume operations are performed using the scsi_eh thread, so
> commands, particularly the sd resume start/stop command, will be
> held off until the device exits error handling. Libata already
> flushes eh with ata_port_wait_eh() in the port teardown paths, so
> there are no concerns with async operation colliding with the
> end-of-life of the ata_port object. Also, libata-core is already
> careful to flush in-flight pm operations before another round of pm
> starts on the given ata_port.
I realize this is a little late but I finally started looking at the
patch set I was working on last year again, and now that I look at
your version that was accepted, I realize that it only addresses the
libata side of things. sd still issues START_STOP_UNIT synchronously
in the resume path, so without the patch fixing that, you shouldn't
see any actual speed up in resume times. Or are you using the
manage_start_stop flag to inhibit that ( at the cost of taking an
emergency park on each suspend/shutdown )?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJUlLjNAAoJENRVrw2cjl5RU48H/2APBJMJ9XyTEfa7r6+M76zH
jf238VwOJUuTUC+Mh2h3AoQVkNy4E8CM/CAnWww8Y1iAvuRTptp9J64NrAQdylCf
p3KLIqhXaGmGvgx1SpzwzwGhbvZ9YM8w1uRC1VLACr9ZwySjEXyEv3B2kZDDUMEj
xxnnQfM47f2km6pxhV7nzt1jHlvaWhvPsuRSaVFxLQstbGR9U1VLJnESZgBFYipR
w5z0dmhssE21A/T8B7dSAx5tDCATeWsMn5fDtQ15MFXgfguXrmmOuHLBtv9EGPZt
d5M1rr2E7WXems5pBoxJMcYFblwQ/h30qPEkRNgYXrfTRx7h79q20tWNI+B1D1c=
=s6tS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-19 23:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 20:17 [PATCH v5 0/3] Accelerate Storage Resume (2x or more) Dan Williams
2014-03-05 20:17 ` [PATCH v5 1/3] libata, libsas: kill pm_result and related cleanup Dan Williams
2014-03-10 20:29 ` Tejun Heo
2014-03-10 20:44 ` Tejun Heo
2014-03-05 20:17 ` [PATCH v5 2/3] libata: async resume Dan Williams
2014-12-19 23:46 ` Phillip Susi [this message]
2014-12-20 1:42 ` Phillip Susi
2014-03-05 20:17 ` [PATCH v5 3/3] scsi: async sd resume Dan Williams
2014-03-07 15:42 ` Alan Stern
2014-03-08 0:41 ` Dan Williams
2014-03-08 2:52 ` Dan Williams
2014-03-10 15:49 ` Alan Stern
2014-03-10 20:43 ` Tejun Heo
2014-03-10 20:56 ` Dan Williams
2014-03-10 20:59 ` Alan Stern
2014-03-10 21:06 ` Dan Williams
2014-03-10 22:41 ` Phillip Susi
2014-03-11 4:19 ` James Bottomley
2014-03-11 4:47 ` Dan Williams
2014-03-11 5:16 ` James Bottomley
2014-03-11 5:26 ` Dan Williams
2014-03-11 6:29 ` James Bottomley
2014-03-14 20:11 ` Dan Williams
2014-03-15 21:47 ` James Bottomley
2014-03-15 23:35 ` Dan Williams
2014-03-16 18:21 ` James Bottomley
2014-03-17 18:20 ` Dan Williams
2014-03-21 0:09 ` Dan Williams
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=5494B8D1.1070608@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=JBottomley@Parallels.com \
--cc=dan.j.williams@intel.com \
--cc=len.brown@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--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 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.