public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
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
Date: Tue, 19 Aug 2008 19:18:49 +0530	[thread overview]
Message-ID: <48AACF41.5090905@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080819.214635.70071441.taka@valinux.co.jp>

Hirokazu Takahashi wrote:
> 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.

I was under the impression that you wanted memory-cgroup to provide the page
movement feature. That is not on the TODO list for us now.

-- 
	Balbir

  reply	other threads:[~2008-08-19 13:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 12:31 [PATCH 0/7] I/O bandwidth controller and BIO tracking Ryo Tsuruta
2008-08-12 12:33 ` [PATCH 1/7] dm-ioband: Patch of device-mapper driver Ryo Tsuruta
2008-08-12 12:34   ` [PATCH 2/7] dm-ioband: Documentation of design overview, installation, command reference and examples Ryo Tsuruta
2008-08-12 12:34     ` [PATCH 3/7] bio-cgroup: Introduction Ryo Tsuruta
2008-08-12 12:35       ` [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts Ryo Tsuruta
2008-08-12 12:36         ` [PATCH 5/7] bio-cgroup: Remove a lot of "#ifdef"s Ryo Tsuruta
2008-08-12 12:36           ` [PATCH 6/7] bio-cgroup: Implement the bio-cgroup Ryo Tsuruta
2008-08-12 12:37             ` [PATCH 7/7] bio-cgroup: Add a cgroup support to dm-ioband Ryo Tsuruta
2008-08-18  1:39         ` [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts KAMEZAWA Hiroyuki
2008-08-19  3:28           ` Ryo Tsuruta
2008-08-19  4:01             ` Balbir Singh
2008-08-19 12:46               ` Hirokazu Takahashi
2008-08-19 13:48                 ` Balbir Singh [this message]
2008-08-20  5:47                   ` Hirokazu Takahashi
  -- strict thread matches above, loose matches on Subject: below --
2008-08-04  8:52 [PATCH 1/7] dm-ioband: Patch of device-mapper driver Ryo Tsuruta
2008-08-04  8:52 ` [PATCH 2/7] dm-ioband: Documentation of design overview, installation, command reference and examples Ryo Tsuruta
2008-08-04  8:57   ` [PATCH 3/7] bio-cgroup: Introduction Ryo Tsuruta
2008-08-04  8:57     ` [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts Ryo Tsuruta
2008-08-05 10:25       ` Andrea Righi
2008-08-05 10:35         ` Hirokazu Takahashi
2008-08-06  7:54       ` KAMEZAWA Hiroyuki
2008-08-06 11:43         ` Hirokazu Takahashi
2008-08-06 13:45         ` kamezawa.hiroyu
2008-08-07  7:25           ` Hirokazu Takahashi
2008-08-07  8:21             ` KAMEZAWA Hiroyuki
2008-08-07  8:45               ` Hirokazu Takahashi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48AACF41.5090905@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=agk@sourceware.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryov@valinux.co.jp \
    --cc=taka@valinux.co.jp \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xemul@openvz.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox