On 04/23, Tejun Heo wrote: > > On 04/23/2010 03:08 AM, Arve Hjønnevåg wrote: > > Allow work to be queued that will block suspend while it is pending > > or executing. To get the same functionality in the calling code often > > requires a separate suspend_blocker for pending and executing work, or > > additional state and locking. > > Hmm... I think this can be implemented as pure wrapper around > workqueue instead of injecting a flag and code into workqueue core. > Adding @fn field to suspend_blocking_work struct and using a custom > work function to call it and then invoke suspend_unblock() should be > enough, right? Oh, dedicated queue functions will be needed too. I > don't think it's wise to meddle with workqueue core code for this. Completely agreed. The patch adds very "strange" hacks into workqueue code to solve the very specific problems. Besides, the patch doesn't look right. suspend_unblock() can be called twice if you use cancel_work(). Perhaps this is not a problem, I dunno. WORK_STRUCT_SUSPEND_BLOCKING needs to ensure that cpu_workqueue_struct has a proper alignment. The unblock code in run_workqueue() is racy, it can unblock after the work was queued on another CPU, cwq->lock can't help. Oleg. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
