From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber Costa Subject: Re: [PATCH v5 14/14] Add documentation about the kmem controller Date: Thu, 18 Oct 2012 13:38:08 +0400 Message-ID: <507FCE00.1090501@parallels.com> References: <1350382611-20579-1-git-send-email-glommer@parallels.com> <1350382611-20579-15-git-send-email-glommer@parallels.com> <20121017151254.e26607c5.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20121017151254.e26607c5.akpm@linux-foundation.org> Sender: owner-linux-mm@kvack.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Andrew Morton Cc: linux-mm@kvack.org, cgroups@vger.kernel.org, Mel Gorman , Tejun Heo , Michal Hocko , Johannes Weiner , kamezawa.hiroyu@jp.fujitsu.com, Christoph Lameter , David Rientjes , Pekka Enberg , devel@openvz.org, linux-kernel@vger.kernel.org, Frederic Weisbecker , Pekka Enberg , Suleiman Souhlal On 10/18/2012 02:12 AM, Andrew Morton wrote: > On Tue, 16 Oct 2012 14:16:51 +0400 > Glauber Costa wrote: > >> +Kernel memory won't be accounted at all until limit on a group is set. This >> +allows for existing setups to continue working without disruption. The limit >> +cannot be set if the cgroup have children, or if there are already tasks in the >> +cgroup. > > What behaviour will usersapce see if "The limit cannot be set"? > write() returns -EINVAL, something like that? > -EBUSY. Will update. -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755188Ab2JRJiT (ORCPT ); Thu, 18 Oct 2012 05:38:19 -0400 Received: from mx2.parallels.com ([64.131.90.16]:37888 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755163Ab2JRJiS (ORCPT ); Thu, 18 Oct 2012 05:38:18 -0400 Message-ID: <507FCE00.1090501@parallels.com> Date: Thu, 18 Oct 2012 13:38:08 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121009 Thunderbird/16.0 MIME-Version: 1.0 To: Andrew Morton CC: , , Mel Gorman , Tejun Heo , Michal Hocko , Johannes Weiner , , Christoph Lameter , David Rientjes , Pekka Enberg , , , Frederic Weisbecker , Pekka Enberg , Suleiman Souhlal Subject: Re: [PATCH v5 14/14] Add documentation about the kmem controller References: <1350382611-20579-1-git-send-email-glommer@parallels.com> <1350382611-20579-15-git-send-email-glommer@parallels.com> <20121017151254.e26607c5.akpm@linux-foundation.org> In-Reply-To: <20121017151254.e26607c5.akpm@linux-foundation.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/18/2012 02:12 AM, Andrew Morton wrote: > On Tue, 16 Oct 2012 14:16:51 +0400 > Glauber Costa wrote: > >> +Kernel memory won't be accounted at all until limit on a group is set. This >> +allows for existing setups to continue working without disruption. The limit >> +cannot be set if the cgroup have children, or if there are already tasks in the >> +cgroup. > > What behaviour will usersapce see if "The limit cannot be set"? > write() returns -EINVAL, something like that? > -EBUSY. Will update.