From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
linux-mm@kvack.org, balbir@linux.vnet.ibm.com,
lizf@cn.fujitsu.com, hugh@veritas.com
Subject: Re: [BUGFIX][PATCH] memcg: charge swapcache to proper memcg
Date: Wed, 11 Mar 2009 08:53:26 +0900 [thread overview]
Message-ID: <20090311085326.403a211d.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090310160856.77deb5c3.akpm@linux-foundation.org>
On Tue, 10 Mar 2009 16:08:56 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 10 Mar 2009 10:07:07 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
>
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -909,13 +909,24 @@ nomem:
> > static struct mem_cgroup *try_get_mem_cgroup_from_swapcache(struct page *page)
> > {
> > struct mem_cgroup *mem;
> > + struct page_cgroup *pc;
> > swp_entry_t ent;
> >
> > + VM_BUG_ON(!PageLocked(page));
> > +
> > if (!PageSwapCache(page))
> > return NULL;
> >
> > - ent.val = page_private(page);
> > - mem = lookup_swap_cgroup(ent);
> > + pc = lookup_page_cgroup(page);
> > + /*
> > + * Used bit of swapcache is solid under page lock.
> > + */
> > + if (PageCgroupUsed(pc))
> > + mem = pc->mem_cgroup;
> > + else {
> > + ent.val = page_private(page);
> > + mem = lookup_swap_cgroup(ent);
> > + }
> > if (!mem)
> > return NULL;
> > if (!css_tryget(&mem->css))
>
> This patch made rather a mess of
> use-css-id-in-swap_cgroup-for-saving-memory-v4.patch.
>
> I temporarily dropped
> use-css-id-in-swap_cgroup-for-saving-memory-v4.patch. Could I have a
> fixed version please?
Okay.
>
> Do we think that this patch
> (memcg-charge-swapcache-to-proper-memcg.patch) shouild be in 2.6.29?
>
please.
Thanks,
-Kame
> --
> 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>
>
--
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>
next prev parent reply other threads:[~2009-03-10 23:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 1:07 Daisuke Nishimura
2009-03-10 2:35 ` KAMEZAWA Hiroyuki
2009-03-10 3:18 ` Daisuke Nishimura
2009-03-10 3:42 ` KAMEZAWA Hiroyuki
2009-03-10 4:33 ` KAMEZAWA Hiroyuki
2009-03-10 4:47 ` Daisuke Nishimura
2009-03-10 5:04 ` KAMEZAWA Hiroyuki
2009-03-10 6:38 ` Daisuke Nishimura
2009-03-10 6:56 ` KAMEZAWA Hiroyuki
2009-03-10 23:08 ` Andrew Morton
2009-03-10 23:53 ` KAMEZAWA Hiroyuki [this message]
2009-03-11 0:43 ` nishimura
2009-03-11 0:47 ` KAMEZAWA Hiroyuki
2009-03-11 3:04 ` [PATCH] use css id in swap cgroup for saving memory v5 KAMEZAWA Hiroyuki
2009-03-11 11:05 ` Hugh Dickins
2009-03-11 17:16 ` Balbir Singh
2009-03-11 23:46 ` KAMEZAWA Hiroyuki
2009-03-11 23:50 ` KAMEZAWA Hiroyuki
2009-03-16 22:25 ` Hugh Dickins
2009-03-19 0:44 ` [PATCH] memcg remvoe redundant message at swapon KAMEZAWA Hiroyuki
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=20090311085326.403a211d.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--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