Re: [PATCH 3/4] writeback: replace custom worker pool implementationwith unbound workqueue

From: Tejun Heo
Date: Thu Mar 21 2013 - 01:07:29 EST

Hello, Dave.

On Thu, Mar 21, 2013 at 12:57:21PM +1100, Dave Chinner wrote:
> When you have a system that has 50+ active filesystems (pretty
> common in the distributed storage environments were every disk has
> it's own filesystem), knowing which filesystem(s) are getting stuck
> in writeback from the sysrq-w or hangcheck output is pretty damn
> important....

Hmm... I guess, then, what we can do is adding a worker description
which is printed out with task dump. ie. A work function can call
work_set_desc(fmt, arg....). It won't be expensive and can be
implemented relatively easily. Does that sound good enough?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at