On Thu, 7 Dec 2006, Andrew Morton wrote:
>
> umm.. Putting a work_struct* into struct cpu_workqueue_struct and then
> doing appropriate things with cpu_workqueue_struct.lock might work.
Yeah, that looks sane. We can't hide anything in "struct work", because we
can't trust it any more once it's been dispatched, but adding a pointer to
the cpu_workqueue_struct that is only used to compare against another
pointer sounds fine.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
