From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: linux-mm@kvack.org, Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Paul Menage <menage@google.com>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
Pavel Emelianov <xemul@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [-mm][PATCH 1/4] Add memrlimit controller documentation (v4)
Date: Fri, 16 May 2008 00:09:15 +0530 [thread overview]
Message-ID: <482C8353.8080008@linux.vnet.ibm.com> (raw)
In-Reply-To: <482C7F70.2020102@qumranet.com>
Avi Kivity wrote:
> Balbir Singh wrote:
>> +
>> +Advantages of providing this feature
>> +
>> +1. Control over virtual address space allows for a cgroup to fail
>> gracefully
>> + i.e., via a malloc or mmap failure as compared to OOM kill when no
>> + pages can be reclaimed.
>>
>
> Do you mean by this, limiting the number of pagetable pages (that are
> pinned in memory), this preventing oom by a cgroup that instantiates
> many pagetables?
>
>
This is not for page tables (that is in the long term TODO list). This is more
for user space calls to mmap(), malloc() or anything that causes the total
virtual memory of the process to go up (in our case cgroups). The motivation is
similar to the motivations of RLIMIT_AS.
--
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-05-15 18:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 13:09 [-mm][PATCH 0/4] Add memrlimit controller (v4) Balbir Singh
2008-05-14 13:09 ` [-mm][PATCH 1/4] Add memrlimit controller documentation (v4) Balbir Singh
2008-05-15 1:20 ` Li Zefan
2008-05-15 18:22 ` Avi Kivity
2008-05-15 18:39 ` Balbir Singh [this message]
2008-05-14 13:09 ` [-mm][PATCH 2/4] Setup the memrlimit controller (v4) Balbir Singh
2008-05-14 13:29 ` Pavel Emelyanov
2008-05-14 13:09 ` [-mm][PATCH 3/4] cgroup mm owner callback changes to add task info (v4) Balbir Singh
2008-05-14 13:09 ` [-mm][PATCH 4/4] Add memrlimit controller accounting and control (v4) Balbir Singh
2008-05-14 13:25 ` Balbir Singh
2008-05-15 2:25 ` Paul Menage
2008-05-15 6:17 ` Balbir Singh
2008-05-15 6:55 ` Paul Menage
2008-05-15 7:03 ` Balbir Singh
2008-05-15 7:39 ` Paul Menage
2008-05-15 8:25 ` Balbir Singh
2008-05-15 15:28 ` Paul Menage
2008-05-15 17:01 ` Balbir Singh
2008-05-17 20:15 ` Balbir Singh
2008-05-17 20:17 ` Balbir Singh
2008-05-14 13:32 ` Pavel Emelyanov
2008-05-14 19:39 ` Balbir Singh
2008-09-18 20:54 ` Andrew Morton
2008-09-18 23:55 ` Balbir Singh
2008-09-19 6:38 ` Balbir Singh
2008-09-19 20:14 ` Andrew Morton
2008-09-19 21:28 ` 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=482C8353.8080008@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--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=skumar@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.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).