linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH] memcg: remove charge variable in unmap_and_move
Date: Tue, 11 Jan 2011 15:35:13 +0900	[thread overview]
Message-ID: <20110111153513.1c09fa21.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <1294725650-4732-1-git-send-email-minchan.kim@gmail.com>

Hi,

On Tue, 11 Jan 2011 15:00:50 +0900
Minchan Kim <minchan.kim@gmail.com> wrote:

> memcg charge/uncharge could be handled by mem_cgroup_[prepare/end]
> migration itself so charge local variable in unmap_and_move lost the role
> since we introduced 01b1ae63c2.
> 
> In addition, the variable name is not good like below.
> 
> int unmap_and_move()
> {
> 	charge = mem_cgroup_prepare_migration(xxx);
> 	..
> 		BUG_ON(charge); <-- BUG if it is charged?
> 		..
> 		uncharge:
> 		if (!charge)    <-- why do we have to uncharge !charge?
> 			mem_group_end_migration(xxx);
> 	..
> }
> 
> So let's remove unnecessary and confusing variable.
> 
> Suggested-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> Signed-off-by: Minchan Kim <minchan.kim@gmail.com>
> Cc: Balbir Singh <balbir@linux.vnet.ibm.com>
> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
>  mm/migrate.c |   12 ++++--------
>  1 files changed, 4 insertions(+), 8 deletions(-)
> 
> diff --git a/mm/migrate.c b/mm/migrate.c
> index b8a32da..e393841 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -623,7 +623,6 @@ static int unmap_and_move(new_page_t get_new_page, unsigned long private,
>  	struct page *newpage = get_new_page(page, private, &result);
>  	int remap_swapcache = 1;
>  	int rcu_locked = 0;
> -	int charge = 0;
>  	struct mem_cgroup *mem = NULL;
>  	struct anon_vma *anon_vma = NULL;
>  
> @@ -662,12 +661,10 @@ static int unmap_and_move(new_page_t get_new_page, unsigned long private,
>  	}
>  
>  	/* charge against new page */
> -	charge = mem_cgroup_prepare_migration(page, newpage, &mem);
> -	if (charge == -ENOMEM) {
> -		rc = -ENOMEM;
> +	rc = mem_cgroup_prepare_migration(page, newpage, &mem);
> +	if (rc == -ENOMEM)
>  		goto unlock;
> -	}
> -	BUG_ON(charge);
> +	BUG_ON(rc);
>  
>  	if (PageWriteback(page)) {
>  		if (!force || !sync)
> @@ -760,8 +757,7 @@ rcu_unlock:
>  	if (rcu_locked)
>  		rcu_read_unlock();
>  uncharge:
> -	if (!charge)
> -		mem_cgroup_end_migration(mem, page, newpage, rc == 0);
> +	mem_cgroup_end_migration(mem, page, newpage, rc == 0);
>  unlock:
>  	unlock_page(page);
>  
I proposed pseud code like above, but it's wrong unfortunately.
If mem_cgroup_prepare_migration() has succeeded, rc is overwritten to 0.
So even if we failed before calling move_to_new_page(), rc is 0 and
mem_cgroup_end_migration() mis-understand this migration has succeeded.

And, it seems to be just a bit off-topic, the place of the comment
"prepare cgroup just returns 0 or -ENOMEM" isn't good, seeing the commit e8589cc1,
which introduced the comment first.

So, we should do like:

	/* charge against new page */
	if (mem_cgroup_end_migration(page, &newpage, &mem)) {
		/* prepare_migration just returns 0 or -ENOMEM */
		rc = -ENOMEM;
		goto unlock;
	}

	if (PageWriteback(page)) {
		...

uncharge:
	mem_cgroup_end_migration(mem, page, newpage, rc == 0);

or, overwrite rc to -EAGAIN again.
I don't stick to checking "BUG_ON(charge)" personally.


Thanks,
Daisuke Nishimura.

--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2011-01-11  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  6:00 Minchan Kim
2011-01-11  6:27 ` KAMEZAWA Hiroyuki
2011-01-11  6:35 ` Daisuke Nishimura [this message]
2011-01-11  8:49   ` Minchan Kim

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=20110111153513.1c09fa21.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.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