Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754289AbYHSMqu (ORCPT ); Tue, 19 Aug 2008 08:46:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753235AbYHSMqm (ORCPT ); Tue, 19 Aug 2008 08:46:42 -0400 Received: from fms-01.valinux.co.jp ([210.128.90.1]:49173 "EHLO mail.valinux.co.jp" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753212AbYHSMql (ORCPT ); Tue, 19 Aug 2008 08:46:41 -0400 Date: Tue, 19 Aug 2008 21:46:35 +0900 (JST) Message-Id: <20080819.214635.70071441.taka@valinux.co.jp> To: balbir@linux.vnet.ibm.com Cc: ryov@valinux.co.jp, kamezawa.hiroyu@jp.fujitsu.com, xen-devel@lists.xensource.com, containers@lists.linux-foundation.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, dm-devel@redhat.com, agk@sourceware.org, xemul@openvz.org, fernando@oss.ntt.co.jp Subject: Re: [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts From: Hirokazu Takahashi In-Reply-To: <48AA4594.1000908@linux.vnet.ibm.com> References: <20080818103938.8b4e8bfa.kamezawa.hiroyu@jp.fujitsu.com> <20080819.122811.59660409.ryov@valinux.co.jp> <48AA4594.1000908@linux.vnet.ibm.com> X-Mailer: Mew version 5.1.52 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1204 Lines: 31 Hi, > >> I'm now writing remove-lock-page-cgroup patches. it works well. > >> please wait for a while... > > > > I'm looking forward to those patches. > > > > By the way, I'm glad if memory-cgroup has a feature which can make a > > page_cgroup move between cgroups with small overhead. It makes > > bio-cgroup improve the accuracy of tracking down pages. > > Page movement can be a very expensive operation and is proportional to the size > of the control group. I think movement should be an optional feature, if we ever > add it. Yes, we should avoid moving pages as far as it is balanced fairly well between groups. But I want to move pages between bio-cgoups in case it started charging quite a few I/O requests to a wrong bio-cgroup. I think it will be okay if pages moves between bio-cgroups, but they don't need to move between memory cgroups. I know the latter is really heavy and the effect seems to be so limited. Thanks, Hirokazu Takahashi. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/