From: Chris Down <chris@chrisdown.name>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: akpm@linux-foundation.org, mhocko@kernel.org, hannes@cmpxchg.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3] mm, memcg: add workingset_restore in memory.stat
Date: Mon, 4 May 2020 16:51:17 +0100 [thread overview]
Message-ID: <20200504155117.GB271310@chrisdown.name> (raw)
In-Reply-To: <20200504153522.11553-1-laoar.shao@gmail.com>
Yafang Shao writes:
>There's a new workingset counter introduced in commit 1899ad18c607 ("mm:
>workingset: tell cache transitions from workingset thrashing"). With the
>help of this counter we can know the workingset is transitioning or
>thrashing. To leverage the benifit of this counter to memcg, we should
>introduce it into memory.stat. Then we could know the workingset of the
>workload inside a memcg better.
Looks fine, thanks!
Acked-by: Chris Down <chris@chrisdown.name>
prev parent reply other threads:[~2020-05-04 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 15:35 Yafang Shao
2020-05-04 15:51 ` Chris Down [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=20200504155117.GB271310@chrisdown.name \
--to=chris@chrisdown.name \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox