From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH] memcg: update document to mention swapoff should be test.
Date: Mon, 19 Jan 2009 16:15:08 +0900 [thread overview]
Message-ID: <20090119161508.f8b9d342.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090119071220.GE6039@balbir.in.ibm.com>
On Mon, 19 Jan 2009 12:42:20 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-01-19 15:57:48]:
>
> > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> >
> > Considering recently found problem:
> > memcg-fix-refcnt-handling-at-swapoff.patch
> >
> > It's better to mention about swapoff behavior in memcg_test document.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> > Documentation/cgroups/memcg_test.txt | 24 ++++++++++++++++++++++--
> > 1 file changed, 22 insertions(+), 2 deletions(-)
> >
> > Index: mmotm-2.6.29-Jan16/Documentation/cgroups/memcg_test.txt
> > ===================================================================
> > --- mmotm-2.6.29-Jan16.orig/Documentation/cgroups/memcg_test.txt
> > +++ mmotm-2.6.29-Jan16/Documentation/cgroups/memcg_test.txt
> > @@ -1,6 +1,6 @@
> > Memory Resource Controller(Memcg) Implementation Memo.
> > -Last Updated: 2008/12/15
> > -Base Kernel Version: based on 2.6.28-rc8-mm.
> > +Last Updated: 2009/1/19
> > +Base Kernel Version: based on 2.6.29-rc2.
> >
> > Because VM is getting complex (one of reasons is memcg...), memcg's behavior
> > is complex. This is a document for memcg's internal behavior.
> > @@ -340,3 +340,23 @@ Under below explanation, we assume CONFI
> > # mount -t cgroup none /cgroup -t cpuset,memory,cpu,devices
> >
> > and do task move, mkdir, rmdir etc...under this.
> > +
> > + 9.7 swapoff.
> > + Besides management of swap is one of complicated parts of memcg,
> > + call path of swap-in at swapoff is not same as usual swap-in path..
> > + It's worth to be tested explicitly.
> > +
> > + For example, test like following is good.
> > + (Shell-A)
> > + # mount -t cgroup none /cgroup -t memory
> > + # mkdir /cgroup/test
> > + # echo 40M > /cgroup/test/memory.limit_in_bytes
> > + # echo 0 > /cgroup/test/tasks
>
> 0? shouldn't this be pid? Potentially echo $$
>
0 is handled as $$ in cgroup/tasks file.
-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>
next prev parent reply other threads:[~2009-01-19 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 6:57 KAMEZAWA Hiroyuki
2009-01-19 7:12 ` Balbir Singh
2009-01-19 7:15 ` KAMEZAWA Hiroyuki [this message]
2009-01-19 8:34 ` Balbir Singh
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=20090119161508.f8b9d342.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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