Re: memrlimit controller merge to mainline

[Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>]

Paul Menage wrote:
> On Fri, Jul 25, 2008 at 8:30 AM, Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> wrote:
>> There are applications that can/need to handle overcommit, just that we are not
>> aware of them fully. Immediately after our meeting, I was pointed to
>> http://www.linuxfoundation.org/en/Carrier_Grade_Linux/Requirements_Alpha1#AVL.4.1_VM_Strict_Over-Commit
> 
> Thanks, that'll be interesting to take a look at.
> 
>>> So I think we'd be complicating some of the vm paths in mainline with
>>> a feature that isn't likely to get a lot of real use.
>>>
>> I did disagree in the meeting
> 
> Yes, but (my impression of) the overall feeling in the meeting was
> that it wasn't yet the right time to push it to mainline.
> 

Yes! I need to test it more and I'll focus more on that front.

>> and there is also the use case of the feature
>> forming the infrastructure for other rlimit controllers.
> 
> Agreed, but that's something for the future.

I'll work on the mlock controller and post that as well.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL