linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: miklos@szeredi.hu, akpm@linux-foundation.org,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: add replace_page_cache_page() function
Date: Thu, 16 Dec 2010 13:05:44 +0100	[thread overview]
Message-ID: <E1PTCae-0007tw-Un@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <20101216100744.e3a417cf.kamezawa.hiroyu@jp.fujitsu.com> (message from KAMEZAWA Hiroyuki on Thu, 16 Dec 2010 10:07:44 +0900)

On Thu, 16 Dec 2010, KAMEZAWA Hiroyuki wrote:
> On Wed, 15 Dec 2010 16:49:58 +0100
> Miklos Szeredi <miklos@szeredi.hu> wrote:
> 
> > From: Miklos Szeredi <mszeredi@suse.cz>
> > 
> > This function basically does:
> > 
> >      remove_from_page_cache(old);
> >      page_cache_release(old);
> >      add_to_page_cache_locked(new);
> > 
> > Except it does this atomically, so there's no possibility for the
> > "add" to fail because of a race.
> > 
> > This is used by fuse to move pages into the page cache.
> > 
> > Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> > ---
> >  fs/fuse/dev.c           |   10 ++++------
> >  include/linux/pagemap.h |    1 +
> >  mm/filemap.c            |   41 +++++++++++++++++++++++++++++++++++++++++
> >  3 files changed, 46 insertions(+), 6 deletions(-)
> > 
> > Index: linux-2.6/mm/filemap.c
> > ===================================================================
> > --- linux-2.6.orig/mm/filemap.c	2010-12-15 16:39:55.000000000 +0100
> > +++ linux-2.6/mm/filemap.c	2010-12-15 16:41:24.000000000 +0100
> > @@ -389,6 +389,47 @@ int filemap_write_and_wait_range(struct
> >  }
> >  EXPORT_SYMBOL(filemap_write_and_wait_range);
> >  
> > +int replace_page_cache_page(struct page *old, struct page *new, gfp_t gfp_mask)
> > +{
> > +	int error;
> > +
> > +	VM_BUG_ON(!PageLocked(old));
> > +	VM_BUG_ON(!PageLocked(new));
> > +	VM_BUG_ON(new->mapping);
> > +
> > +	error = mem_cgroup_cache_charge(new, current->mm,
> > +					gfp_mask & GFP_RECLAIM_MASK);
> 
> Hmm, then, the page will be recharged to "current" instead of the memcg
> where "old" was under control. Is this design ? If so, why ?

No, I just haven't thought about it.

Porbably charging "new" to where "old" was charged is the logical
thing to do here.

> 
> In mm/migrate.c, following is called.
> 
> 	 charge = mem_cgroup_prepare_migration(page, newpage, &mem);
> 	....do migration....
>         if (!charge)
>                 mem_cgroup_end_migration(mem, page, newpage);
> 
> BTW, off topic, in fuse/dev.c
> 
> add_to_page_cache_locked(page)

This is the call which the above patch replaces with
replace_page_cache_page().  So if I fix replace_page_cache_page() to
charge "newpage" to the correct memory cgroup, that should solve all
problems, no?

Thanks for the review.

Miklos

--
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>

  reply	other threads:[~2010-12-16 12:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 15:49 Miklos Szeredi
2010-12-15 16:49 ` Rik van Riel
2010-12-15 23:22 ` Minchan Kim
2010-12-16 11:59   ` Miklos Szeredi
2010-12-16 22:04     ` Minchan Kim
2010-12-17  1:21       ` Hugh Dickins
2010-12-17  1:40         ` Minchan Kim
2010-12-17  2:10           ` Hugh Dickins
2010-12-17  4:37             ` Minchan Kim
2010-12-17 15:53           ` Miklos Szeredi
2010-12-16  1:07 ` KAMEZAWA Hiroyuki
2010-12-16 12:05   ` Miklos Szeredi [this message]
2010-12-17  0:01     ` KAMEZAWA Hiroyuki
2010-12-17 15:51       ` Miklos Szeredi
2010-12-19 23:54         ` KAMEZAWA Hiroyuki
2011-01-07 18:22 Miklos Szeredi
2011-01-11  2:29 ` KAMEZAWA Hiroyuki
2011-01-11  3:53   ` Daisuke Nishimura
2011-01-11  9:38     ` Miklos Szeredi
2011-01-11  5:41 ` 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=E1PTCae-0007tw-Un@pomaz-ex.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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