| 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: Wed, 16 Feb 2011 09:22:28 -0800 From: Divyesh Shah <dpshah@...gle.com> To: Gui Jianfeng <guijianfeng@...fujitsu.com> Cc: Vivek Goyal <vgoyal@...hat.com>, Jens Axboe <axboe@...nel.dk>, Shaohua Li <shaohua.li@...el.com>, lkml <linux-kernel@...r.kernel.org>, Chad Talbott <ctalbott@...gle.com> Subject: Re: [PATCH 5/6 v4] cfq-iosched: CFQ group hierarchical scheduling and use_hierarchy interface On Tue, Feb 15, 2011 at 5:44 PM, Gui Jianfeng <guijianfeng@...fujitsu.com> wrote: > Hmm, it seems memcg aggregating stats in parent group. > But do we really need to do that in kernel? I think it's easier to do it in > userland, and it makes kernel much simpler. > I would prefer having stats aggregated up the hierarchy. One trick we used at Google earlier was to do lazy updates for most stats. So we would accumulate stats for a given timeslice and at the end of that timeslice propagate those counts all the way up to the parent. For device info like this, the update can be instantaneous since its not a very frequent event. It would also be very useful to distinguish between stats for the cgroup itself vs total values accumulated from the subtree rooted at that cgroup like memcg does. -- Thanks, Divyesh -- 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