Nicholas Swenson da415a096f bcache: Fix moving_gc deadlocking with a foreground write
Deadlock happened because a foreground write slept, waiting for a bucket
to be allocated. Normally the gc would mark buckets available for invalidation.
But the moving_gc was stuck waiting for outstanding writes to complete.
These writes used the bcache_wq, the same queue foreground writes used.

This fix gives moving_gc its own work queue, so it was still finish moving
even if foreground writes are stuck waiting for allocation. It also makes
work queue a parameter to the data_insert path, so moving_gc can use its
workqueue for writes.

Signed-off-by: Nicholas Swenson <nks@daterainc.com>
Signed-off-by: Kent Overstreet <kmo@daterainc.com>
2014-03-18 12:22:33 -07:00
..
2014-02-14 16:13:00 -08:00
2014-02-14 10:40:47 +01:00
2014-01-29 20:00:13 -08:00
2014-01-25 13:19:10 -08:00
2014-02-14 16:13:00 -08:00
2014-01-26 11:00:41 -08:00
2014-02-14 10:33:45 -08:00
2014-02-14 10:32:28 -08:00
2014-01-15 14:51:22 -08:00
2014-01-27 08:15:51 -08:00
2014-02-14 16:14:11 -08:00
2014-02-13 11:12:00 -08:00
2014-01-22 22:24:35 -08:00
2014-02-12 12:28:05 -08:00