From: "Michal Koutný" <mkoutny@suse.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
Muchun Song <songmuchun@bytedance.com>,
Michal Hocko <mhocko@kernel.org>, Roman Gushchin <guro@fb.com>,
Huang Ying <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] memcg: periodically flush the memcg stats
Date: Thu, 24 Jun 2021 16:01:26 +0200 [thread overview]
Message-ID: <YNSQNu4ZW7mEX6LW@blackbook> (raw)
In-Reply-To: <20210615174435.4174364-2-shakeelb@google.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
Hello Shakeel.
On Tue, Jun 15, 2021 at 10:44:35AM -0700, Shakeel Butt <shakeelb@google.com> wrote:
> At the moment memcg stats are read in four contexts:
>
> 1. memcg stat user interfaces
> 2. dirty throttling
> 3. page fault
> 4. memory reclaim
Sorry for being dense or ignorant -- what do you refer to with the point
no. 3 (memcg stats reader during page fault)?
Thanks,
Michal
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-24 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 17:44 [PATCH v2 1/2] memcg: switch lruvec stats to rstat Shakeel Butt
2021-06-15 17:44 ` Shakeel Butt
2021-06-15 17:44 ` [PATCH v2 2/2] memcg: periodically flush the memcg stats Shakeel Butt
2021-06-15 17:44 ` Shakeel Butt
2021-06-15 17:44 ` Shakeel Butt
2021-06-15 19:29 ` Johannes Weiner
2021-06-15 19:29 ` Johannes Weiner
2021-06-15 21:52 ` Shakeel Butt
2021-06-15 21:52 ` Shakeel Butt
2021-06-24 17:46 ` Johannes Weiner
2021-06-24 17:46 ` Johannes Weiner
2021-06-24 14:01 ` Michal Koutný [this message]
2021-06-24 15:00 ` Shakeel Butt
2021-06-24 15:00 ` Shakeel Butt
2021-06-24 15:00 ` Shakeel Butt
2021-07-05 5:30 ` [PATCH v2 1/2] memcg: switch lruvec stats to rstat Huang, Ying
2021-07-05 5:30 ` Huang, Ying
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=YNSQNu4ZW7mEX6LW@blackbook \
--to=mkoutny@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=tj@kernel.org \
--cc=ying.huang@intel.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 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.