Messages in this thread | | | Date | Tue, 19 Mar 2013 10:28:24 -0700 | Subject | Re: [PATCH 3/4] writeback: replace custom worker pool implementation with unbound workqueue | From | Tejun Heo <> |
| |
Hello, Jan.
On Tue, Mar 19, 2013 at 8:46 AM, Jan Kara <jack@suse.cz> wrote: > Well, but what you often get is just output of sysrq-w, or sysrq-t, or > splat from scheduler about stuck task. You often don't have the comfort of > tracing... Can't we somehow change 'comm' of the task when it starts > processing work of some bdi?
You sure can but I'd prefer not to do that. If you wanna do it properly, you have to grab task lock every time a work item starts execution. I'm not sure how beneficial having the block device identifier would be. Backtrace would be there the same. Is identifying the block device that important?
Thanks.
-- tejun
| |