linux-kernel - Re: [mm][PATCH 0/4] Memory cgroup hierarchy introduction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081104091510.01cf3a1e.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Tue, 4 Nov 2008 09:15:10 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Balbir Singh <balbir@...ux.vnet.ibm.com>
Cc:	linux-mm@...ck.org, YAMAMOTO Takashi <yamamoto@...inux.co.jp>,
	Paul Menage <menage@...gle.com>, lizf@...fujitsu.com,
	linux-kernel@...r.kernel.org,
	Nick Piggin <nickpiggin@...oo.com.au>,
	David Rientjes <rientjes@...gle.com>,
	Pavel Emelianov <xemul@...nvz.org>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [mm][PATCH 0/4] Memory cgroup hierarchy introduction

On Sun, 02 Nov 2008 00:18:12 +0530
Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:

> This patch follows several iterations of the memory controller hierarchy
> patches. The hardwall approach by Kamezawa-San[1]. Version 1 of this patchset
> at [2].
> 
> The current approach is based on [2] and has the following properties
> 
> 1. Hierarchies are very natural in a filesystem like the cgroup filesystem.
>    A multi-tree hierarchy has been supported for a long time in filesystems.
>    When the feature is turned on, we honor hierarchies such that the root
>    accounts for resource usage of all children and limits can be set at
>    any point in the hierarchy. Any memory cgroup is limited by limits
>    along the hierarchy. The total usage of all children of a node cannot
>    exceed the limit of the node.
> 2. The hierarchy feature is selectable and off by default
> 3. Hierarchies are expensive and the trade off is depth versus performance.
>    Hierarchies can also be completely turned off.
> 
> The patches are against 2.6.28-rc2-mm1 and were tested in a KVM instance
> with SMP and swap turned on.
> 

As first impression, I think hierarchical LRU management is not good...means
not fair from viewpoint of memory management.
I'd like to show some other possible implementation of
try_to_free_mem_cgroup_pages() if I can.

Anyway, I have to merge this with mem+swap 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/