Messages in this thread | | | Date | Thu, 18 Oct 2007 19:48:19 +0400 | From | Oleg Nesterov <> | Subject | Re: [PATCH] flush_work_sync vs. flush_scheduled_work Re: [PATCH] PHYLIB: IRQ event workqueue handling fixes |
| |
On 10/18, Jarek Poplawski wrote: > > +/** > + * flush_work_sync - block until a work_struct's callback has terminated ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Hmm...
> + * Similar to cancel_work_sync() but will only busy wait (without cancel) > + * if the work is queued.
Yes, it won't block, but will spin in busy-wait loop until all other works scheduled before this work are finished. Not good. After that it really blocks waiting for this work to complete.
And I am a bit confused. We can't use flush_workqueue() because some of the queued work_structs may take rtnl_lock, yes? But in that case we can't use the new flush_work_sync() helper as well, no?
If we can't just cancel the work, can't we do something like
if (cancel_work_sync(w)) w->func(w);
instead?
> +void flush_work_sync(struct work_struct *work) > +{ > + int ret; > + > + do { > + ret = work_pending(work); > + wait_on_work(work); > + if (ret) > + cpu_relax(); > + } while (ret); > +}
If we really the new helper, perhaps we can make it a bit better?
1. Modify insert_work() to take the "struct list_head *at" parameter instead of "int tail". I think this patch will also cleanup the code a bit, and shrink a couple of bytes from .text
2. flush_work_sync() inserts a barrier right after this work and blocks. We still need some retry logic to handle the queueing is in progress of course, but we won't spin waiting for the other works.
What do you think?
Oleg.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |