From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hugh@veritas.com>,
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,
taka@valinux.co.jp, linux-mm@kvack.org,
David Rientjes <rientjes@google.com>
Subject: Re: [RFC][1/3] Add user interface for virtual address space control (v2)
Date: Thu, 27 Mar 2008 15:16:40 +0530 [thread overview]
Message-ID: <47EB6D00.5070306@linux.vnet.ibm.com> (raw)
In-Reply-To: <47EB6B4D.2030305@openvz.org>
Pavel Emelyanov wrote:
> KAMEZAWA Hiroyuki wrote:
>> On Thu, 27 Mar 2008 00:20:06 +0530
>> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>>
>>> Add as_usage_in_bytes and as_limit_in_bytes interfaces. These provide
>>> control over the total address space that the processes combined together
>>> in the cgroup can grow upto. This functionality is analogous to
>>> the RLIMIT_AS function of the getrlimit(2) and setrlimit(2) calls.
>>> A as_res resource counter is added to the mem_cgroup structure. The
>>> as_res counter handles all the accounting associated with the virtual
>>> address space accounting and control of cgroups.
>>>
>>> Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
>> I wonder that it's better to create "rlimit cgroup" rather than enhancing
>> memory controller. (But I have no strong opinion.)
>> How do you think ?
>
> I believe that all memory management is better to have in one controller...
>
Paul wants to see it in a different controller. He has been reasoning it out in
another email thread.
--
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-27 9:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 18:49 [RFC][0/3] Virtual address space control for cgroups (v2) Balbir Singh
2008-03-26 18:50 ` [RFC][1/3] Add user interface for virtual address space control (v2) Balbir Singh
2008-03-27 9:14 ` KAMEZAWA Hiroyuki
2008-03-27 9:39 ` Pavel Emelyanov
2008-03-27 9:46 ` Balbir Singh [this message]
2008-03-26 18:50 ` [RFC][2/3] Account and control virtual address space allocations (v2) Balbir Singh
2008-03-26 19:10 ` Balbir Singh
2008-03-27 7:19 ` Pavel Emelyanov
2008-03-27 8:02 ` Balbir Singh
2008-03-27 8:24 ` Pavel Emelyanov
2008-03-27 8:30 ` Balbir Singh
2008-03-27 8:38 ` Pavel Emelyanov
2008-03-26 18:50 ` [RFC][3/3] Update documentation for virtual address space control (v2) Balbir Singh
2008-03-26 22:22 ` [RFC][0/3] Virtual address space control for cgroups (v2) Paul Menage
2008-03-27 8:04 ` Balbir Singh
2008-03-27 14:28 ` Paul Menage
2008-03-27 17:50 ` Balbir Singh
2008-03-27 18:44 ` Paul Menage
2008-03-28 3:59 ` Balbir Singh
2008-03-28 14:37 ` Paul Menage
2008-03-28 18:13 ` Balbir Singh
2008-03-27 10:03 ` KAMEZAWA Hiroyuki
2008-03-27 13:59 ` Paul Menage
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=47EB6D00.5070306@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.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=rientjes@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=taka@valinux.co.jp \
--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