From: Dongsheng Yang <yangds.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [RESEND PATCH 2/2] cpuacct: split usage into user_usage and sys_usage.
Date: Tue, 22 Dec 2015 16:12:20 +0800 [thread overview]
Message-ID: <567905E4.70108@cn.fujitsu.com> (raw)
In-Reply-To: <20151221213328.GP4026-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
On 12/22/2015 05:33 AM, Tejun Heo wrote:
> 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.
>
> cpuusage is being phased out. If you need these stats, please
> implement it on cpu side.
Hi TJ, thanx, then I will look at introducing this feature in cpu side
then.
Thanx
Yang
>
> Thanks.
>
WARNING: multiple messages have this Message-ID (diff)
From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
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.
Date: Tue, 22 Dec 2015 16:12:20 +0800 [thread overview]
Message-ID: <567905E4.70108@cn.fujitsu.com> (raw)
In-Reply-To: <20151221213328.GP4026@mtj.duckdns.org>
On 12/22/2015 05:33 AM, Tejun Heo wrote:
> 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.
>
> cpuusage is being phased out. If you need these stats, please
> implement it on cpu side.
Hi TJ, thanx, then I will look at introducing this feature in cpu side
then.
Thanx
Yang
>
> Thanks.
>
next prev parent reply other threads:[~2015-12-22 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 11:14 [RESEND PATCH 1/2] cpuacct: rename parameter in cpuusage_write for readability Dongsheng Yang
2015-12-21 11:14 ` Dongsheng Yang
2015-12-21 11:14 ` [RESEND PATCH 2/2] cpuacct: split usage into user_usage and sys_usage Dongsheng Yang
2015-12-21 11:14 ` Dongsheng Yang
[not found] ` <1450696483-2864-2-git-send-email-yangds.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-12-21 21:33 ` Tejun Heo
2015-12-21 21:33 ` Tejun Heo
[not found] ` <20151221213328.GP4026-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2015-12-22 8:12 ` Dongsheng Yang [this message]
2015-12-22 8:12 ` Dongsheng Yang
2016-03-01 10:35 ` Zhao Lei
2016-03-01 10:35 ` Zhao Lei
2016-03-02 16:12 ` 'Tejun Heo'
2016-03-21 11:17 ` [tip:sched/urgent] sched/cpuacct: Rename parameter in cpuusage_write() for readability tip-bot for Dongsheng Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=567905E4.70108@cn.fujitsu.com \
--to=yangds.fnst-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.