From: Minchan Kim <minchan.kim@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
kamezawa.hiroyu@jp.fujitsu.com, nishimura@mxp.nes.nec.co.jp,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mm: add replace_page_cache_page() function
Date: Wed, 19 Jan 2011 10:24:09 +0900 [thread overview]
Message-ID: <AANLkTimh7jq7HLjfxVX0XKdhOhWEQtDn-faGc+iJ-ykd@mail.gmail.com> (raw)
In-Reply-To: <20110118152844.88cfdc2c.akpm@linux-foundation.org>
On Wed, Jan 19, 2011 at 8:28 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 18 Jan 2011 12:18:11 +0100
> Miklos Szeredi <miklos@szeredi.hu> wrote:
>
>> +int replace_page_cache_page(struct page *old, struct page *new, gfp_t gfp_mask)
>> +{
>> + int error;
>> + struct mem_cgroup *memcg = NULL;
>
> I'm suspecting that the unneeded initialisation was added to suppress a
> warning?
>
> I removed it, and didn't get a warning. I expected to.
>
> Really, uninitialized_var() is better. It avoids adding extra code
> and, unlike "= 0" it is self-documenting.
>
>> + VM_BUG_ON(!PageLocked(old));
>> + VM_BUG_ON(!PageLocked(new));
>> + VM_BUG_ON(new->mapping);
>> +
>> + /*
>> + * This is not page migration, but prepare_migration and
>> + * end_migration does enough work for charge replacement.
>> + *
>> + * In the longer term we probably want a specialized function
>> + * for moving the charge from old to new in a more efficient
>> + * manner.
>> + */
>> + error = mem_cgroup_prepare_migration(old, new, &memcg, gfp_mask);
>> + if (error)
>> + return error;
>> +
>> + error = radix_tree_preload(gfp_mask & ~__GFP_HIGHMEM);
>> + if (!error) {
>> + struct address_space *mapping = old->mapping;
>> + pgoff_t offset = old->index;
>> +
>> + page_cache_get(new);
>> + new->mapping = mapping;
>> + new->index = offset;
>> +
>> + spin_lock_irq(&mapping->tree_lock);
>> + __remove_from_page_cache(old);
>> + error = radix_tree_insert(&mapping->page_tree, offset, new);
>> + BUG_ON(error);
>> + mapping->nrpages++;
>> + __inc_zone_page_state(new, NR_FILE_PAGES);
>> + if (PageSwapBacked(new))
>> + __inc_zone_page_state(new, NR_SHMEM);
>> + spin_unlock_irq(&mapping->tree_lock);
>> + radix_tree_preload_end();
>> + page_cache_release(old);
>> + mem_cgroup_end_migration(memcg, old, new, true);
>
> This is all pretty ugly and inefficient.
>
> We call __remove_from_page_cache() which does a radix-tree lookup and
> then fiddles a bunch of accounting things.
>
> Then we immediately do the same radix-tree lookup and then undo the
> accounting changes which we just did. And we do it in an open-coded
> fashion, thus giving the kernel yet another code site where various
> operations need to be kept in sync.
>
> Would it not be better to do a single radix_tree_lookup_slot(),
> overwrite the pointer therein and just leave all the ancilliary
> accounting unaltered?
I agree single radix_tree_lookup but accounting still is needed since
newpage could be on another zone. What we can remove is just only
mapping->nrpages.
--
Kind regards,
Minchan Kim
--
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>
next prev parent reply other threads:[~2011-01-19 1:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 11:18 [PATCH v4] mm: add replace_page_cache_page() function Miklos Szeredi
2011-01-18 23:28 ` Andrew Morton
2011-01-19 0:27 ` Daisuke Nishimura
2011-01-19 0:41 ` Andrew Morton
2011-01-19 0:48 ` KAMEZAWA Hiroyuki
2011-01-19 1:11 ` nishimura
2011-01-19 1:23 ` KAMEZAWA Hiroyuki
2011-01-21 5:52 ` Daisuke Nishimura
2011-01-21 6:17 ` KAMEZAWA Hiroyuki
2011-01-19 0:33 ` KAMEZAWA Hiroyuki
2011-01-19 1:24 ` Minchan Kim [this message]
2011-01-19 1:48 ` Andrew Morton
2011-01-19 2:17 ` Minchan Kim
2011-09-08 23:52 ` Andrew Morton
2011-09-09 1:43 ` KAMEZAWA Hiroyuki
2011-01-19 1:17 ` 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=AANLkTimh7jq7HLjfxVX0XKdhOhWEQtDn-faGc+iJ-ykd@mail.gmail.com \
--to=minchan.kim@gmail.com \
--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 \
--cc=miklos@szeredi.hu \
--cc=nishimura@mxp.nes.nec.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).