Re: [PATCH 3/4] writeback: replace custom worker pool implementationwith unbound workqueue
From: Tejun Heo
Date: Mon Mar 18 2013 - 18:35:36 EST
On Mon, Mar 18, 2013 at 11:32:44PM +0100, Jan Kara wrote:
> I realized there may be one issue - so far we have a clear identification
> which thread works for which bdi in the thread name (flush-x:y naming).
> That was useful when debugging things. Now with your worker pool this is
> lost, am I right? Would it be possible to restore that?
Unfortunately not directly. It shouldn't be difficult to tell who's
working on what from workqueue and writeback tracepoints tho.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/