linux-kernel - Re: [PATCH 0/4] Provide cpuacct functionality in cpu cgroup

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Nov 2011 09:57:06 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Glauber Costa <glommer@...allels.com>
Cc:	linux-kernel@...r.kernel.org, paul@...lmenage.org,
	lizf@...fujitsu.com, daniel.lezcano@...e.fr,
	a.p.zijlstra@...llo.nl, jbottomley@...allels.com, pjt@...gle.com,
	cgroups@...r.kernel.org
Subject: Re: [PATCH 0/4] Provide cpuacct functionality in cpu cgroup

On Tue, 15 Nov 2011 13:59:13 -0200
Glauber Costa <glommer@...allels.com> wrote:

> Hi,
> 
> This is an excerpt of the last patches I sent regarding cpu cgroup.
> It is mostly focused on cleaning up what we have now, so it can
> be considered largely preparation. As a user of the new organization
> of things, I am including cpuacct stats functionality in the end of
> the series. The files related to cpuusage are left to be sent in
> an upcoming series after this one is included.
> 
> Let me know if there is anything you'd like me to address.
> 

I'm sorry but let me several questions.

Why cpu cgroup but cpuacct cgroup ?
If scheduler stat is reported via cpu cgroup, it makes sense.
If user accounting information is reported via cpu cgroup, I feel it's strange.
Do you want to make cpuacct cgroup obsolete and merge 2 cgroups ?

What's relationship between this new counters and cpuacct cgroup ?
Aren't users confused ?

Please provide Documenation.

 
Thanks,
-Kame

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