WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

[Xen-devel] Re: [PATCH 6/7] bio-cgroup: Implement the bio-cgroup

To: yoshikawa.takuya@xxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH 6/7] bio-cgroup: Implement the bio-cgroup
From: Ryo Tsuruta <ryov@xxxxxxxxxxxxx>
Date: 2008年8月08日 20:41:13 +0900 (JST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, containers@xxxxxxxxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, dm-devel@xxxxxxxxxx, agk@xxxxxxxxxxxxxx
Delivery-date: 2008年8月08日 04:41:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <489C150C.5040700@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <489BF14D.6050009@xxxxxxxxxxxxx> <20080808.173045.112614776.ryov@xxxxxxxxxxxxx> <489C150C.5040700@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Yoshikawa-san,
> I wanted to test my own scheduler which uses bio tracking information.
> SO I tried your patch, especially, get_bio_cgroup_iocontext(), to get
> the io_context from bio.
>
> In my test, I made some threads with certain iopriorities run
> concurrently. To schedule these threads based on their iopriorities,
> I made BGROUP directories for each iopriorities.
> e.g. /cgroup/bio/be0 ... /cgroup/bio/be7
> Then, I tried to attach the processes to the appropriate groups.
>
> But the processes stayed in the original group(id=0).
In the current implementation, when a process moves to an another cgroup:
 - Already allocated memory does not move to the cgroup, still remains.
 - Only allocated memory after move belongs to the cgroup.
This behavior follows the memory controller.
Memory does not move between cgroups since it is so heavy operation, 
but it would be worth under some sort of conditions.
Could you try to move a process between cgroups in the following way?
 # echo $$ > /cgroup/bio/be0
 # run_your_program
 # echo $$ > /cgroup/bio/be1
 # run_your_program
 ...
> I am sorry but I have to leave now and I cannot come here next week.
> --> I will take summer holidays.
Have a nice vacation!
Thanks,
Ryo Tsuruta
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-devel] Re: RFC: I/O bandwidth controller , Hirokazu Takahashi
Next by Date: [Xen-devel] [PATCH] linux/acpi: more extcntl code adjustments , Jan Beulich
Previous by Thread: [Xen-devel] Re: [PATCH 6/7] bio-cgroup: Implement the bio-cgroup , Ryo Tsuruta
Next by Thread: [Xen-devel] Re: [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts , Hirokazu Takahashi
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /