From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, Hugh Dickins <hughd@google.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Glauber Costa <glommer@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] memcg: change behavior of moving charges at task move
Date: Thu, 22 Mar 2012 11:17:20 -0400 [thread overview]
Message-ID: <1332429440-7167-1-git-send-email-n-horiguchi@ah.jp.nec.com> (raw)
In-Reply-To: <4F69A4C4.4080602@jp.fujitsu.com>
On Wed, Mar 21, 2012 at 06:52:04PM +0900, KAMEZAWA Hiroyuki wrote:
> As discussed before, I post this to fix the spec and implementation of task moving.
> Then, do you think what target kernel version should be ? 3.4/3.5 ?
> but yes, it may be late for 3.4....
>
> ==
> In documentation, it's said that 'shared anon are not moved'.
> But in implementation, the check was wrong.
>
> if (!move_anon() || page_mapcount(page) > 2)
>
> Ah, memcg has been moving shared anon pages for a long time.
>
> Then, here is a discussion about handling of shared anon pages.
>
> - It's complex
> - Now, shared file caches are moved in force.
> - It adds unclear check as page_mapcount(). To do correct check,
> we should check swap users, etc.
> - No one notice this implementation behavior. So, no one get benefit
> from the design.
> - In general, once task is moved to a cgroup for running, it will not
> be moved....
> - Finally, we have control knob as memory.move_charge_at_immigrate.
>
> Here is a patch to allow moving shared pages, completely. This makes
> memcg simpler and fix current broken code.
>
> Note:
> IIUC, libcgroup's cgroup daemon moves tasks after exec().
> So, it's not affected.
> libcgroup's command "cgexec" does move itsef to a memcg and call exec()
> without fork(). it's not affected.
>
> Changelog:
> - fixed PageAnon() check.
> - remove call of lookup_swap_cache()
> - fixed Documentation.
>
> Suggested-by: Hugh Dickins <hughd@google.com>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
It looks good to me.
Reviewed-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Thanks,
Naoya
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-03-22 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 9:52 KAMEZAWA Hiroyuki
2012-03-22 15:17 ` Naoya Horiguchi [this message]
2012-03-22 21:29 ` Andrew Morton
2012-03-23 0:05 ` KAMEZAWA Hiroyuki
2012-03-22 21:36 ` Andrew Morton
2012-03-23 0:18 ` KAMEZAWA Hiroyuki
2012-03-23 0:30 ` Andrew Morton
2012-03-23 0:52 ` KAMEZAWA Hiroyuki
2012-03-23 8:53 ` Johannes Weiner
2012-03-23 9:00 ` KAMEZAWA Hiroyuki
2012-03-23 9:45 ` Michal Hocko
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=1332429440-7167-1-git-send-email-n-horiguchi@ah.jp.nec.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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