[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47EB6B4D.2030305@openvz.org>
Date: Thu, 27 Mar 2008 12:39:25 +0300
From: Pavel Emelyanov <xemul@...nvz.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Balbir Singh <balbir@...ux.vnet.ibm.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Hugh Dickins <hugh@...itas.com>,
Sudhir Kumar <skumar@...ux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@...inux.co.jp>,
Paul Menage <menage@...gle.com>, lizf@...fujitsu.com,
linux-kernel@...r.kernel.org, taka@...inux.co.jp,
linux-mm@...ck.org, David Rientjes <rientjes@...gle.com>
Subject: Re: [RFC][1/3] Add user interface for virtual address space control
(v2)
KAMEZAWA Hiroyuki wrote:
> On Thu, 27 Mar 2008 00:20:06 +0530
> Balbir Singh <balbir@...ux.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@...ux.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...
> Thanks,
> -Kame
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists