similar to: [PATCH 0/8] I/O bandwidth controller and BIO tracking

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi everyone, This is dm-ioband version 0.0.3 release. 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. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, This is dm-ioband version 0.0.3 release. 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. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, This is dm-ioband version 0.0.3 release. 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. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. 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. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. 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. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. 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. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi Alasdair and all, This is the dm-ioband version 1.10.5 release. This patch can be applied cleanly to current agk's tree. The only change from the previous version is that some blktrace messages are added by Alan D. Brunelle, thanks Alan. Alasdair, Could you please tell me your opinion about merging dm-ioband to upstream? What else do I have to do? Is there any possibility that dm-ioband

Hi Alasdair and all, This is the dm-ioband version 1.10.5 release. This patch can be applied cleanly to current agk's tree. The only change from the previous version is that some blktrace messages are added by Alan D. Brunelle, thanks Alan. Alasdair, Could you please tell me your opinion about merging dm-ioband to upstream? What else do I have to do? Is there any possibility that dm-ioband

Hi Alasdair and all, This is the dm-ioband version 1.10.5 release. This patch can be applied cleanly to current agk's tree. The only change from the previous version is that some blktrace messages are added by Alan D. Brunelle, thanks Alan. Alasdair, Could you please tell me your opinion about merging dm-ioband to upstream? What else do I have to do? Is there any possibility that dm-ioband

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major changes of these releases are: - dm-ioband can be configured through the cgroup interface. The bandwidth can be assigned on a per cgroup per block device basis. - The event tracing is supported that helps in debugging and monitoring dm-ioband. - A document for blkio-cgroup is available at

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major changes of these releases are: - dm-ioband can be configured through the cgroup interface. The bandwidth can be assigned on a per cgroup per block device basis. - The event tracing is supported that helps in debugging and monitoring dm-ioband. - A document for blkio-cgroup is available at

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major changes of these releases are: - dm-ioband can be configured through the cgroup interface. The bandwidth can be assigned on a per cgroup per block device basis. - The event tracing is supported that helps in debugging and monitoring dm-ioband. - A document for blkio-cgroup is available at

Hi all, This is a new release of bio-cgroup which provides an IO tracking mechanism. The patches can be applied to the kernel 2.6.30-rc1 and you can also download them from the following site. http://people.valinux.co.jp/~ryov/bio-cgroup/ What's bio-cgroup all about? ============================ With this feature, you can determine the owners of any type of I/Os. This makes

Hi all, This is a new release of bio-cgroup which provides an IO tracking mechanism. The patches can be applied to the kernel 2.6.30-rc1 and you can also download them from the following site. http://people.valinux.co.jp/~ryov/bio-cgroup/ What's bio-cgroup all about? ============================ With this feature, you can determine the owners of any type of I/Os. This makes

Hi all, This is a new release of bio-cgroup which provides an IO tracking mechanism. The patches can be applied to the kernel 2.6.30-rc1 and you can also download them from the following site. http://people.valinux.co.jp/~ryov/bio-cgroup/ What's bio-cgroup all about? ============================ With this feature, you can determine the owners of any type of I/Os. This makes

Hi everyone, Here are new releases of bio-cgroup. Changes from the previous version are as follows: - Accurate dirty-page tracking Support migrating pages between bio-cgroups with minimum overhead, but I think such a situation is quite rare. - Fix a bug of swapcache page handling Sometimes, "bad page state" is occurred since the memory controller has temporarily changed the

Hi everyone, Here are new releases of bio-cgroup. Changes from the previous version are as follows: - Accurate dirty-page tracking Support migrating pages between bio-cgroups with minimum overhead, but I think such a situation is quite rare. - Fix a bug of swapcache page handling Sometimes, "bad page state" is occurred since the memory controller has temporarily changed the