| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20130319154600.GC5222@quack.suse.cz> Date: Tue, 19 Mar 2013 16:46:00 +0100 From: Jan Kara <jack@...e.cz> To: Tejun Heo <tj@...nel.org> Cc: Jan Kara <jack@...e.cz>, axboe@...nel.dk, laijs@...fujitsu.com, fengguang.wu@...el.com, linux-kernel@...r.kernel.org, jmoyer@...hat.com Subject: Re: [PATCH 3/4] writeback: replace custom worker pool implementation with unbound workqueue On Mon 18-03-13 15:35:26, Tejun Heo wrote: > 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. 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? Honza -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists