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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4E7CA9B1.9070903@parallels.com>
Date:	Fri, 23 Sep 2011 12:45:53 -0300
From:	Glauber Costa <glommer@...allels.com>
To:	Balbir Singh <bsingharora@...il.com>
CC:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
	<linux-kernel@...r.kernel.org>, <xemul@...allels.com>,
	<paul@...lmenage.org>, <lizf@...fujitsu.com>,
	<daniel.lezcano@...e.fr>, <mingo@...e.hu>,
	<jbottomley@...allels.com>
Subject: Re: [PATCH 1/9] Remove parent field in cpuacct cgroup

On 09/23/2011 05:09 AM, Balbir Singh wrote:
>>> Android makes heavy use of cpuacct as well. We invented it to do cpu
>>> accounting independent of control
>>
>> But its a massive waste of time to have to iterate a double hierarchy,
>> cache-miss heaven.
>>
>
> By double hierarchy you mean both cpu and cpuacct? What if they are
> not mounted together?
>
>> Or so people really have independent cgroups as well? I thought people
>> just co-mount all this crap.
>>
>
> Please see
> http://code.google.com/p/cgroupmgr/wiki/cgroupsForAndroid
> http://stackoverflow.com/questions/6814207/android-cpuacct-usage-file
>
> AFAIK, some versions mount cpuacct at /acct and independent of cpu cgroups
>
> Balbir
But then, are they using both cpuacct and cpu cgroup for an independent 
group of tasks?

The problem here is that we're gathering the same statistics 3 times 
just because we need/want to present then in a different way. This is 
really bad design.


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ