From: Michal Hocko <mhocko@suse.cz>
To: Qiang Huang <h.huangqiang@huawei.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
bsingharora@gmail.com, kamezawa.hiroyu@jp.fujitsu.com,
Cgroups <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Li Zefan <lizefan@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] memcg: correct comments for __mem_cgroup_begin_update_page_stat
Date: Wed, 7 May 2014 11:19:39 +0200 [thread overview]
Message-ID: <20140507091939.GB9489@dhcp22.suse.cz> (raw)
In-Reply-To: <5369EE61.1040003@huawei.com>
On Wed 07-05-14 16:27:13, Qiang Huang wrote:
>
> Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
Looks good
Acked-by: Michal Hocko <mhocko@suse.cz>
Thanks!
> ---
> mm/memcontrol.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 5804d71..f96e68e 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -2251,12 +2251,11 @@ cleanup:
> }
>
> /*
> - * Currently used to update mapped file statistics, but the routine can be
> - * generalized to update other statistics as well.
> + * Used to update mapped file or writeback or other statistics.
> *
> * Notes: Race condition
> *
> - * We usually use page_cgroup_lock() for accessing page_cgroup member but
> + * We usually use lock_page_cgroup() for accessing page_cgroup member but
> * it tends to be costly. But considering some conditions, we doesn't need
> * to do so _always_.
> *
> @@ -2270,8 +2269,8 @@ cleanup:
> * by flags.
> *
> * Considering "move", this is an only case we see a race. To make the race
> - * small, we check mm->moving_account and detect there are possibility of race
> - * If there is, we take a lock.
> + * small, we check memcg->moving_account and detect there are possibility
> + * of race or not. If there is, we take a lock.
> */
>
> void __mem_cgroup_begin_update_page_stat(struct page *page,
> --
> 1.8.3
>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-05-07 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 8:27 Qiang Huang
2014-05-07 9:19 ` Michal Hocko [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=20140507091939.GB9489@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=h.huangqiang@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizefan@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