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
| ||
|
Date: Fri, 17 Feb 2012 15:06:43 -0800 From: Tejun Heo <tj@...nel.org> To: Vivek Goyal <vgoyal@...hat.com> Cc: Kent Overstreet <koverstreet@...gle.com>, axboe@...nel.dk, ctalbott@...gle.com, rni@...gle.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 7/9] block: implement bio_associate_current() On Fri, Feb 17, 2012 at 05:56:15PM -0500, Vivek Goyal wrote: > BTW, blk-throttle mangling the context, is a real problem you are facing > or it is just one of things which is nice to fix. Yeah, it is a real problem which makes blk-throttle useless if cfq propio is in use. > If a cgroup is being throttled do people really care about the > iopriority of original task that much. (Given the fact that > iopriority helps only so much and kills performance on fast > storage). Yeap, apparently, people wanna apply hard limits on top of propio. Besides, it's just bad to mangle cgroup *randomly* as the current code does. Thanks. -- tejun -- 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