Thread (6 messages) 6 messages, 3 authors, 2016-03-02

RE: [RESEND PATCH 2/2] cpuacct: split usage into user_usage and sys_usage.

From: Zhao Lei <hidden>
Date: 2016-03-01 10:36:23
Also in: lkml

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 <redacted>
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:
quoted
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:

1: Only put new stats into cpu side, and don't change old interface,
   we'll see following content in cgroup dir:
   /cgroup/cpuacct:
     cpuacct.usage
     cpuacct.usage_percpu
   /cgroup/cpu:
     cpu.usage_sys
     cpu.usage_percpu_sys
     cpu.usage_user
     cpu.usage_percpu_user
   It is obviously not unify.
2: Move old stats into cpu side, and add new stats:
   we'll see following content in cgroup dir:
   /cgroup/cpuacct:
     [NONE]
   /cgroup/cpu:
     cpu.usage
     cpu.usage_percpu
     cpu.usage_sys
     cpu.usage_percpu_sys
     cpu.usage_user
     cpu.usage_percpu_user
   It have compatibility issues with old system.
3: Clone old stats into cpu side(share one copy of code), and add new stats
   Into cpu side, we'll see following content in cgroup dir:
   /cgroup/cpuacct:
     cpuacct.usage
     cpuacct.usage_percpu
   /cgroup/cpu:
     cpu.usage
     cpu.usage_percpu
     cpu.usage_sys
     cpu.usage_percpu_sys
     cpu.usage_user
     cpu.usage_percpu_user
   It can support both old and new systems, and we can remove old interface
   in future, but we if mount both cpu and cpuacct into same dir,
   we'll see following duplicated files:
   /cgroup/cpu,cpuacct
     cpu.usage
     cpuacct.usage
     cpu.usage_percpu
     cpuacct.usage_percpu
     ...

Maybe above way3 looks having less defect, cound you talk about
your opinion on it.

Thanks
Zhaolei



Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help