From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Thelen Subject: Re: [PATCH v4 02/11] memcg: document cgroup dirty memory interfaces Date: Fri, 29 Oct 2010 14:37:30 -0700 Message-ID: References: <1288336154-23256-1-git-send-email-gthelen@google.com> <1288336154-23256-3-git-send-email-gthelen@google.com> <20101029131952.1191023d.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <20101029131952.1191023d.akpm@linux-foundation.org> (Andrew Morton's message of "Fri, 29 Oct 2010 13:19:52 -0700") Sender: owner-linux-mm@kvack.org To: Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, containers@lists.osdl.org, Andrea Righi , Balbir Singh , KAMEZAWA Hiroyuki , Daisuke Nishimura , Minchan Kim , Ciju Rajan K , David Rientjes , Wu Fengguang List-Id: containers.vger.kernel.org Andrew Morton writes: > On Fri, 29 Oct 2010 00:09:05 -0700 > Greg Thelen wrote: > >> Document cgroup dirty memory interfaces and statistics. >> >> >> ... >> >> +When use_hierarchy=0, each cgroup has dirty memory usage and limits. >> +System-wide dirty limits are also consulted. Dirty memory consumption is >> +checked against both system-wide and per-cgroup dirty limits. >> + >> +The current implementation does enforce per-cgroup dirty limits when > > "does not", I trust. Correct. Thanks. >> +use_hierarchy=1. System-wide dirty limits are used for processes in such >> +cgroups. Attempts to read memory.dirty_* files return the system-wide values. >> +Writes to the memory.dirty_* files return error. An enhanced implementation is >> +needed to check the chain of parents to ensure that no dirty limit is exceeded. >> + >> 6. Hierarchy support >> >> The memory controller supports a deep hierarchy and hierarchical accounting. >> -- >> 1.7.3.1 > > -- > 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 -- 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 S1762036Ab0J2VjI (ORCPT ); Fri, 29 Oct 2010 17:39:08 -0400 Received: from smtp-out.google.com ([216.239.44.51]:29490 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756019Ab0J2VjH (ORCPT ); Fri, 29 Oct 2010 17:39:07 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=from:to:cc:subject:references:date:in-reply-to:message-id: user-agent:mime-version:content-type; b=qsPEIjawE/b0WWNrG7tRonoMlxpHVL+dU2DK4U/l2v6XGcPZ8rV3qFTR/NdCnpUOQ teZdgdKgYkYW+wPpJBHqQ== From: Greg Thelen To: Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, containers@lists.osdl.org, Andrea Righi , Balbir Singh , KAMEZAWA Hiroyuki , Daisuke Nishimura , Minchan Kim , Ciju Rajan K , David Rientjes , Wu Fengguang Subject: Re: [PATCH v4 02/11] memcg: document cgroup dirty memory interfaces References: <1288336154-23256-1-git-send-email-gthelen@google.com> <1288336154-23256-3-git-send-email-gthelen@google.com> <20101029131952.1191023d.akpm@linux-foundation.org> Date: Fri, 29 Oct 2010 14:37:30 -0700 In-Reply-To: <20101029131952.1191023d.akpm@linux-foundation.org> (Andrew Morton's message of "Fri, 29 Oct 2010 13:19:52 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrew Morton writes: > On Fri, 29 Oct 2010 00:09:05 -0700 > Greg Thelen wrote: > >> Document cgroup dirty memory interfaces and statistics. >> >> >> ... >> >> +When use_hierarchy=0, each cgroup has dirty memory usage and limits. >> +System-wide dirty limits are also consulted. Dirty memory consumption is >> +checked against both system-wide and per-cgroup dirty limits. >> + >> +The current implementation does enforce per-cgroup dirty limits when > > "does not", I trust. Correct. Thanks. >> +use_hierarchy=1. System-wide dirty limits are used for processes in such >> +cgroups. Attempts to read memory.dirty_* files return the system-wide values. >> +Writes to the memory.dirty_* files return error. An enhanced implementation is >> +needed to check the chain of parents to ensure that no dirty limit is exceeded. >> + >> 6. Hierarchy support >> >> The memory controller supports a deep hierarchy and hierarchical accounting. >> -- >> 1.7.3.1 > > -- > 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