From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber Costa Subject: Re: [PATCH v3 6/7] tcp buffer limitation: per-cgroup limit Date: Sat, 24 Sep 2011 14:27:34 -0300 Message-ID: <4E7E1306.9060200@parallels.com> References: <1316393805-3005-1-git-send-email-glommer@parallels.com> <1316393805-3005-7-git-send-email-glommer@parallels.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , , , , , , , , To: Andi Kleen Return-path: In-Reply-To: Sender: owner-linux-mm@kvack.org List-Id: netdev.vger.kernel.org On 09/24/2011 01:58 PM, Andi Kleen wrote: > Glauber Costa writes: > >> This patch uses the "tcp_max_mem" field of the kmem_cgroup to >> effectively control the amount of kernel memory pinned by a cgroup. >> >> We have to make sure that none of the memory pressure thresholds >> specified in the namespace are bigger than the current cgroup. > > I noticed that some other OS known by bash seem to have a rlimit per > process for this. Would that make sense too? Not sure how difficult > your infrastructure would be to extend to that. > > -Andi > Well, not that hard, I believe. and given the benchmarks I've run in this iteration, I think it wouldn't be that much of a performance impact either. We just need to account it to a task whenever we account it for a control group. Now that the functions where accounting are done are abstracted away, it is even quite few places to touch. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org