Tejun Heo 2ca32b4848 [SCSI] fcoe: use dedicated workqueue instead of system_wq ... fcoe uses the system_wq to destroy ports and the work items need to be flushed before the driver is unloaded. As the work items free the containing data structure, they can't be flushed directly. The workqueue should be flushed instead. Also, the destruction works can be chained - ie. destruction of a port may lead to destruction of another port where the work item for the former queues the work for the latter. Currently, the depth of chain can be at most two and fcoe_exit() makes sure everything is complete by calling flush_scheduled_work() twice. With commit c8efcc25 (workqueue: allow chained queueing during destruction), destroy_workqueue() can take care of chained works on workqueue destruction. Add and use fcoe_wq instead. Simply destroying fcoe_wq on driver unload takes care of flushing. Signed-off-by: Tejun Heo <tj@kernel.org> Signed-off-by: Robert Love <robert.w.love@intel.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>		2011-02-12 11:17:50 -06:00
..
fcoe_ctlr.c	[SCSI] libfcoe: include fcoe_transport.c into kernel libfcoe module	2011-02-12 11:06:52 -06:00
fcoe_transport.c	[SCSI] libfcoe: include fcoe_transport.c into kernel libfcoe module	2011-02-12 11:06:52 -06:00
fcoe.c	[SCSI] fcoe: use dedicated workqueue instead of system_wq	2011-02-12 11:17:50 -06:00
fcoe.h	[SCSI] fcoe: Formatting cleanups and commenting	2009-12-04 12:01:08 -06:00
libfcoe.h	[SCSI] libfcoe: add implementation to support fcoe transport	2011-02-12 11:06:06 -06:00
Makefile	[SCSI] libfcoe: include fcoe_transport.c into kernel libfcoe module	2011-02-12 11:06:52 -06:00