From: Roman Gushchin <guro@fb.com>
To: Xu Yu <xuyu@linux.alibaba.com>
Cc: "cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"mhocko@kernel.org" <mhocko@kernel.org>,
"vdavydov.dev@gmail.com" <vdavydov.dev@gmail.com>
Subject: Re: [PATCH] mm, memcg: fix comment error about memory.low usage
Date: Mon, 23 Dec 2019 16:52:59 +0000 [thread overview]
Message-ID: <20191223165254.GA17129@localhost.localdomain> (raw)
In-Reply-To: <0505ec19cc077cf32d7175ffea121e2130c64590.1577090923.git.xuyu@linux.alibaba.com>
On Mon, Dec 23, 2019 at 04:56:56PM +0800, Xu Yu wrote:
> When memory.current > memory.low, the usage of memory.low should be the
> value of memory.low, not 0.
>
> Fix and simplify the equation in comments.
Hello, Xu!
There is a pending patchset from Johannes, which performs a significant rework
of this code: https://lkml.org/lkml/2019/12/19/1272 .
Please, take a look.
Thanks!
prev parent reply other threads:[~2019-12-23 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 8:56 Xu Yu
2019-12-23 16:52 ` Roman Gushchin [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=20191223165254.GA17129@localhost.localdomain \
--to=guro@fb.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=xuyu@linux.alibaba.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