On Sunday 20 December 2009, Alan Stern wrote: > On Sun, 20 Dec 2009, Rafael J. Wysocki wrote: > > > So, seriously, do you think it makes sense to do asynchronous suspend at all? > > I'm asking, because we're likely to get into troubles like this during suspend > > for other kinds of devices too and without resolving them we won't get any > > significant speedup from asynchronous suspend. > > > > That said, to me it's definitely worth doing asynchronous resume with the > > "start asynch threads upfront" modification, as the results of the tests show > > that quite clearly. I hope you agree. > > It's too early to come to this sort of conclusion (i.e., that suspend > and resume react very differently to an asynchronous approach). Unless > you have some definite _reason_ for thinking that resume will benefit > more than suspend, you shouldn't try to generalize so much from tests > on only two systems. In fact I have one reason. Namely, the things that drivers do on suspend and resume are evidently quite different and on these two systems I was able to test they apparently took different amounts of time to complete. The very fact that on both systems resume is substantially longer than suspend, even if all devices are suspended and resumed synchronously, is quite interesting. Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
