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
Subject: Re: [PATCH 0/2] cpu subsystem for unified hierarchy.
Date: Fri, 15 Jan 2016 08:44:09 +0800 [thread overview]
Message-ID: <569840D9.8050302@cn.fujitsu.com> (raw)
In-Reply-To: <20160114215749.GE3520-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
On 01/15/2016 05:57 AM, Tejun Heo wrote:
> Hello, Dongsheng.
>
> On Wed, Jan 13, 2016 at 04:40:18PM +0800, Dongsheng Yang wrote:
>> Hi TJ,
>> When I want to improve cpuacct subsystem, you said we are going
>> to combine cpuacct and cpu subsystem. Then I am here to try to implement
>> cpu subsystem in unified hierarchy and squash cpuacct in it.
>
> There's already a patchset pending.
>
> http://lkml.kernel.org/g/20160105164758.GD5995-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org
Oops, I found I lost the emails in cgroup list recently, so I did not
get your patch about it. Sorry for the duplication about this work.
I will find back what I lost these days and figure out what I should
do based on your work.
Thanx
Yang
>
> Thanks.
>
prev parent reply other threads:[~2016-01-15 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 8:40 [PATCH 0/2] cpu subsystem for unified hierarchy Dongsheng Yang
[not found] ` <1452674420-31603-1-git-send-email-yangds.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2016-01-13 8:40 ` [PATCH 1/2] sched: implement " Dongsheng Yang
2016-01-13 8:40 ` [PATCH 2/2] cgroup: cpu subsystem: split cpu usage into user_usage and sys_usage Dongsheng Yang
2016-01-14 21:57 ` [PATCH 0/2] cpu subsystem for unified hierarchy Tejun Heo
[not found] ` <20160114215749.GE3520-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-01-15 0:44 ` Dongsheng Yang [this message]
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=569840D9.8050302@cn.fujitsu.com \
--to=yangds.fnst-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@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.