On Friday, December 20, 2013 08:32:20 AM Tejun Heo wrote: > Hello, Rafael. > > On Fri, Dec 20, 2013 at 02:31:37AM +0100, Rafael J. Wysocki wrote: > > > If this looks good to you, I'll commit it to wq/for-3.14 and we can at > > > least start to clean up things. > > > > Yes, it does. > > > > So with that I need to do workqueue_set_max_active(wq, WQ_FROZEN_ACTIVE) > > during > > suspend and then workqueue_set_max_active(wq, WQ_DFL_ACTIVE) during resume > > on > > my workqueue, right? > > Yeah, you can also do workqueue_set_max_active(wq, 0) during resume to > restore the default value, which is what's used by alloc_workqueue() > anyway.
OK > I'll apply the two patches to wq/for-3.14 once David reviews them or > if you wanna take them through the pm tree, that's fine too. I don't > have anything scheduled for wq for the next merge window. I have some material queued up, so I can take them once they've been reviewed. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
