From: "lujialin (A)" <lujialin4@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeelb@google.com>,
Muchun Song <songmuchun@bytedance.com>,
Xiu Jianfeng <xiujianfeng@huawei.com>, <cgroups@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [RFC 0/2] Introduce cgroup.top interface
Date: Fri, 26 Aug 2022 17:50:55 +0800 [thread overview]
Message-ID: <e6deb22b-506d-d4f6-1a75-58dda4b58bcc@huawei.com> (raw)
In-Reply-To: <Ywg7NcHtfjDKjwXR@slm.duckdns.org>
Ok, I got it, thanks
在 2022/8/26 11:17, Tejun Heo 写道:
> Hello,
>
> On Fri, Aug 26, 2022 at 09:15:01AM +0800, Lu Jialin wrote:
>> Cgroup is used to organize and manage resource available processes.
>> Currently there are no handy tool for gathering reousrce usage
>> information for each and every child cgroups, makes it hard to detect
>> resource outage and debug resource issues.
>>
>> To overcome this, we present the cgroup.top interface. Just like the
>> top command, user is able to easily gather resource usage information
>> , allowing user to detect and respond to resource outage in child
>> cgroups
> I don't think this is something we want build into the kernel. Maybe what
> you want is something similar to below?
>
> https://github.com/facebookincubator/below
>
> Thanks.
>
prev parent reply other threads:[~2022-08-26 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 1:15 Lu Jialin
2022-08-26 1:15 ` [RFC 1/2] cgroup: Introduce per-cgroup resource top show interface Lu Jialin
2022-08-26 1:15 ` [RFC 2/2] memcg: Adapt cgroup.top into per-memcg Lu Jialin
2022-08-26 7:38 ` Michal Hocko
2022-08-26 3:17 ` [RFC 0/2] Introduce cgroup.top interface Tejun Heo
2022-08-26 9:50 ` lujialin (A) [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=e6deb22b-506d-d4f6-1a75-58dda4b58bcc@huawei.com \
--to=lujialin4@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=tj@kernel.org \
--cc=xiujianfeng@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox