Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756216AbcCBQMw (ORCPT ); Wed, 2 Mar 2016 11:12:52 -0500 Received: from mail-yk0-f181.google.com ([209.85.160.181]:33625 "EHLO mail-yk0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755613AbcCBQMr (ORCPT ); Wed, 2 Mar 2016 11:12:47 -0500 Date: Wed, 2 Mar 2016 11:12:44 -0500 From: "'Tejun Heo'" To: Zhao Lei Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, peterz@infradead.org Subject: Re: [RESEND PATCH 2/2] cpuacct: split usage into user_usage and sys_usage. Message-ID: <20160302161244.GC29826@mtj.duckdns.org> References: <1450696483-2864-1-git-send-email-yangds.fnst@cn.fujitsu.com> <1450696483-2864-2-git-send-email-yangds.fnst@cn.fujitsu.com> <20151221213328.GP4026@mtj.duckdns.org> <010801d173a6$237a2d70$6a6e8850$@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <010801d173a6$237a2d70$6a6e8850$@cn.fujitsu.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1263 Lines: 38 Hello, On Tue, Mar 01, 2016 at 06:35:56PM +0800, Zhao Lei wrote: > Hi, Tejun Heo > > > From: linux-kernel-owner@vger.kernel.org > > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Tejun Heo > > Sent: Tuesday, December 22, 2015 5:33 AM > > To: Dongsheng Yang > > Cc: cgroups@vger.kernel.org; linux-kernel@vger.kernel.org; > > mingo@redhat.com; peterz@infradead.org > > Subject: Re: [RESEND PATCH 2/2] cpuacct: split usage into user_usage and > > sys_usage. > > > > On Mon, Dec 21, 2015 at 07:14:43PM +0800, Dongsheng Yang wrote: > > > Sometimes, cpuacct.usage is not detialed enough to user > > > to see how much usage a group used. We want to know how > > > much time it used in user mode and how much in kernel mode. > > > Yang gave this patch to me :) > I'm plan to continue this function. > > > cpuusage is being phased out. If you need these stats, please > > implement it on cpu side. > > Currently, old stats are put in cpuacct, if we put new stats into cpu side, > we have following way: Yeah, on the second thought, at least for now, I think it's best to put this in cpuacct. We can do the trafer to the cpu controller later. Please feel free to add Acked-by: Tejun Heo Thanks. -- tejun