| 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: <20130321113252.GA30777@quack.suse.cz> Date: Thu, 21 Mar 2013 12:32:52 +0100 From: Jan Kara <jack@...e.cz> To: Tejun Heo <tj@...nel.org> Cc: Dave Chinner <david@...morbit.com>, 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 Wed 20-03-13 22:07:18, Tejun Heo wrote: > 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? Yeah, that sounds good! Thanks! 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