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] [PATCH 0/7] I/O bandwidth controller and BIO tracking

To: linux-kernel@xxxxxxxxxxxxxxx, dm-devel@xxxxxxxxxx, containers@xxxxxxxxxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0/7] I/O bandwidth controller and BIO tracking
From: Ryo Tsuruta <ryov@xxxxxxxxxxxxx>
Date: 2008年8月04日 17:51:26 +0900 (JST)
Cc: agk@xxxxxxxxxxxxxx
Delivery-date: 2008年8月04日 01:51:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi everyone,
This series of patches of dm-ioband now includes "The bio tracking mechanism,"
which has been posted individually to this mailing list.
This makes it easy for anybody to control the I/O bandwidth even when
the I/O is one of delayed-write requests.
Have fun!
This series of patches consists of two parts:
 1. dm-ioband
 Dm-ioband is an I/O bandwidth controller implemented as a
 device-mapper driver, which gives specified bandwidth to each job
 running on the same physical device. A job is a group of processes
 with the same pid or pgrp or uid or a virtual machine such as KVM
 or Xen. A job can also be a cgroup by applying the bio-cgroup patch.
 2. bio-cgroup
 Bio-cgroup is a BIO tracking mechanism, which is implemented on
 the cgroup memory subsystem. With the mechanism, it is able to
 determine which cgroup each of bio belongs to, even when the bio
 is one of delayed-write requests issued from a kernel thread
 such as pdflush.
The above two parts have been posted individually to this mailing list
until now, but after this time we would release them all together.
 [PATCH 1/7] dm-ioband: Patch of device-mapper driver
 [PATCH 2/7] dm-ioband: Documentation of design overview, installation,
 command reference and examples.
 [PATCH 3/7] bio-cgroup: Introduction
 [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts
 [PATCH 5/7] bio-cgroup: Remove a lot of "#ifdef"s
 [PATCH 6/7] bio-cgroup: Implement the bio-cgroup
 [PATCH 7/7] bio-cgroup: Add a cgroup support to dm-ioband
Please see the following site for more information:
 Linux Block I/O Bandwidth Control Project
 http://people.valinux.co.jp/~ryov/bwctl/
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: Re: [Xen-devel] Bug for Xen-3.3.0-rc2: libpci read error. No emulation. , Yuji Shimada
Next by Date: [Xen-devel] [PATCH 1/7] dm-ioband: Patch of device-mapper driver , Ryo Tsuruta
Previous by Thread: [Xen-devel] [PATCH] xend: Fix handling of pci creation failure in device_create() , Yosuke Iwamatsu
Next by Thread: [Xen-devel] [PATCH 1/7] dm-ioband: Patch of device-mapper driver , Ryo Tsuruta
Indexes: [Date] [Thread] [Top] [All Lists]

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

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