From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Paul Menage <menage@google.com>,
Pavel Emelianov <xemul@openvz.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Linux Containers <containers@lists.osdl.org>
Subject: Re: [PATCH 2/3] memcg: put a restriction on writing memory.force_empty
Date: Tue, 11 Mar 2008 15:45:06 +0530 [thread overview]
Message-ID: <47D65BAA.60908@linux.vnet.ibm.com> (raw)
In-Reply-To: <47D65A36.4020008@cn.fujitsu.com>
Li Zefan wrote:
> We can write whatever to memory.force_empty:
>
> echo 999 > memory.force_empty
> echo wow > memory.force_empty
>
> This is odd, so let's make '1' to be the only valid value.
I suspect as long as there is no unreasonable side-effect, writing 999 or wow
should be OK.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Paul Menage <menage@google.com>,
Pavel Emelianov <xemul@openvz.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Linux Containers <containers@lists.osdl.org>
Subject: Re: [PATCH 2/3] memcg: put a restriction on writing memory.force_empty
Date: Tue, 11 Mar 2008 15:45:06 +0530 [thread overview]
Message-ID: <47D65BAA.60908@linux.vnet.ibm.com> (raw)
In-Reply-To: <47D65A36.4020008@cn.fujitsu.com>
Li Zefan wrote:
> We can write whatever to memory.force_empty:
>
> echo 999 > memory.force_empty
> echo wow > memory.force_empty
>
> This is odd, so let's make '1' to be the only valid value.
I suspect as long as there is no unreasonable side-effect, writing 999 or wow
should be OK.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
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:[~2008-03-11 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 10:08 [PATCH 2/3] memcg: put a restriction on writing memory.force_empty Li Zefan
2008-03-11 10:08 ` Li Zefan
2008-03-11 10:15 ` Balbir Singh [this message]
2008-03-11 10:15 ` Balbir Singh
2008-03-11 10:23 ` KAMEZAWA Hiroyuki
2008-03-11 10:23 ` 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=47D65BAA.60908@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.