From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber Costa Subject: Re: [PATCH v3 3/6] expose fine-grained per-cpu data for cpuacct stats Date: Wed, 30 May 2012 17:26:24 +0400 Message-ID: <4FC62000.9070704@parallels.com> References: <1338371317-5980-1-git-send-email-glommer@parallels.com> <1338371317-5980-4-git-send-email-glommer@parallels.com> <4FC6107F.9020802@parallels.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Paul Turner Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, devel@openvz.org, Peter Zijlstra , Tejun Heo , "Eric W. Biederman" , handai.szj@gmail.com, Andrew.Phillips@lmax.com, Serge Hallyn On 05/30/2012 04:48 PM, Paul Turner wrote: >> > Now, if you guys are okay with a file per-cpu, I can do it as well. >> > It pollutes the filesystem, but at least protects against the fact that this >> > is kmalloc-backed. >> > > As I prefaced, I'm not sure there's much that can be trivially done > about it. This is really a fundamental limitation of how read_map() > works. > > What we really need is a proper seq_file exposed through cftypes. Tejun, would you be okay with an interface that exports somehow the raw seq_file in cgroups ? This way we could call s_show for each cpu and get away with the memory usage problem, I presume