linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Chris Down <chris@chrisdown.name>,
	Andrew Morton <akpm@linux-foundation.org>,
	Cgroups <cgroups@vger.kernel.org>, Linux MM <linux-mm@kvack.org>,
	shaoyafang@didiglobal.com
Subject: Re: [PATCH] mm/memcg: add allocstall to memory.stat
Date: Fri, 12 Apr 2019 11:36:41 +0200	[thread overview]
Message-ID: <20190412093641.GG13373@dhcp22.suse.cz> (raw)
In-Reply-To: <CALOAHbAcXDDdq_XO+hvwTq6PMNjFFgHAY2OPmkAReKV8-wR6sg@mail.gmail.com>

On Fri 12-04-19 17:29:04, Yafang Shao wrote:
> On Fri, Apr 12, 2019 at 5:09 PM Michal Hocko <mhocko@kernel.org> wrote:
[...]
> > > Then we can do some trace for this memcg, i.e. to trace how long the
> > > applicatons may stall via tracepoint.
> > > (but current tracepoints can't trace a specified cgroup only, that's
> > > another point to be improved.)
> >
> > It is a task that is stalled, not a cgroup.
> 
> But these tracepoints can't filter a speficied task neither.

each trace line output should cotain a pid, no?
-- 
Michal Hocko
SUSE Labs


  reply	other threads:[~2019-04-12  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 11:59 Yafang Shao
2019-04-11 12:26 ` Michal Hocko
2019-04-11 12:41   ` Yafang Shao
2019-04-11 13:39     ` Michal Hocko
2019-04-11 13:54       ` Yafang Shao
2019-04-11 15:10         ` Michal Hocko
2019-04-12  1:32           ` Yafang Shao
2019-04-12  6:34             ` Michal Hocko
2019-04-12  8:10               ` Yafang Shao
2019-04-12  9:09                 ` Michal Hocko
2019-04-12  9:29                   ` Yafang Shao
2019-04-12  9:36                     ` Michal Hocko [this message]
2019-04-12  9:48                       ` Yafang Shao

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=20190412093641.GG13373@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chris@chrisdown.name \
    --cc=hannes@cmpxchg.org \
    --cc=laoar.shao@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=shaoyafang@didiglobal.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