similar to: IO controller Mini-Summit 2009

Hi All, As I have notified before, The 1st Linux IO controller Mini-Summit will be held in Tokyo Japan on Oct 17 -- day before the 9th Linux kernel summit. So I would like to propose the following topics for the mini-summit and discuss about them. - Multiple IO controller development projects - There are two activities for the development of IO controller, Vivek's io-controller and

Hi All, As I have notified before, The 1st Linux IO controller Mini-Summit will be held in Tokyo Japan on Oct 17 -- day before the 9th Linux kernel summit. So I would like to propose the following topics for the mini-summit and discuss about them. - Multiple IO controller development projects - There are two activities for the development of IO controller, Vivek's io-controller and

Hi All, As I have notified before, The 1st Linux IO controller Mini-Summit will be held in Tokyo Japan on Oct 17 -- day before the 9th Linux kernel summit. So I would like to propose the following topics for the mini-summit and discuss about them. - Multiple IO controller development projects - There are two activities for the development of IO controller, Vivek's io-controller and

Hi All, I have got excellent results of dm-ioband, that controls the disk I/O bandwidth even when it accepts delayed write requests. In this time, I ran some benchmarks with a high-end storage. The reason was to avoid a performance bottleneck due to mechanical factors such as seek time. You can see the details of the benchmarks at: http://people.valinux.co.jp/~ryov/dm-ioband/hps/ Thanks, Ryo

Hi All, I have got excellent results of dm-ioband, that controls the disk I/O bandwidth even when it accepts delayed write requests. In this time, I ran some benchmarks with a high-end storage. The reason was to avoid a performance bottleneck due to mechanical factors such as seek time. You can see the details of the benchmarks at: http://people.valinux.co.jp/~ryov/dm-ioband/hps/ Thanks, Ryo

Hi All, I have got excellent results of dm-ioband, that controls the disk I/O bandwidth even when it accepts delayed write requests. In this time, I ran some benchmarks with a high-end storage. The reason was to avoid a performance bottleneck due to mechanical factors such as seek time. You can see the details of the benchmarks at: http://people.valinux.co.jp/~ryov/dm-ioband/hps/ Thanks, Ryo

Hi All, We will hold a Linux IO controller Mini-Summit in Tokyo, Japan on Saturday, Oct. 17, 2009 -- day before the 9th Linux kernel summit. This is a good opportunity to meet face-to-face to discuss issues and directions for developing IO controller. Details of the summit are still sketchy, so suggestions for agenda topics are welcome. Please e-mail to me or post on the wiki page at

Hi All, We will hold a Linux IO controller Mini-Summit in Tokyo, Japan on Saturday, Oct. 17, 2009 -- day before the 9th Linux kernel summit. This is a good opportunity to meet face-to-face to discuss issues and directions for developing IO controller. Details of the summit are still sketchy, so suggestions for agenda topics are welcome. Please e-mail to me or post on the wiki page at

Hi All, We will hold a Linux IO controller Mini-Summit in Tokyo, Japan on Saturday, Oct. 17, 2009 -- day before the 9th Linux kernel summit. This is a good opportunity to meet face-to-face to discuss issues and directions for developing IO controller. Details of the summit are still sketchy, so suggestions for agenda topics are welcome. Please e-mail to me or post on the wiki page at

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

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

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

Hi everyone, I have a question about cgroup's policy concerning the treatment of threads. Please consider that we want to attach an application which has some threads already to a certain cgroup. If we echo the pid of this application to the "tasks" file connected to this cgroup the threads belonging to this application will NOT be moved to the new group. Is it right? If so, is

Hi everyone, I have a question about cgroup's policy concerning the treatment of threads. Please consider that we want to attach an application which has some threads already to a certain cgroup. If we echo the pid of this application to the "tasks" file connected to this cgroup the threads belonging to this application will NOT be moved to the new group. Is it right? If so, is

Hi everyone, This is a new release of dm-ioband and bio-cgroup. With this release, the overhead of bio-cgroup is significantly reduced and the accuracy of block I/O tracking is much improved. These patches are for 2.6.28-rc2-mm1. Enjoy it! 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

Hi everyone, This is a new release of dm-ioband and bio-cgroup. With this release, the overhead of bio-cgroup is significantly reduced and the accuracy of block I/O tracking is much improved. These patches are for 2.6.28-rc2-mm1. Enjoy it! 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

Hi everyone, This is a new release of dm-ioband and bio-cgroup. With this release, the overhead of bio-cgroup is significantly reduced and the accuracy of block I/O tracking is much improved. These patches are for 2.6.28-rc2-mm1. Enjoy it! 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

Hi Alasdair and all, This is the dm-ioband version 1.8.0 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. This release is a minor bug fix and confirmed running on the latest stable kernel 2.6.27.1. - Can be applied to the kernel 2.6.27.1 and 2.6.27-rc5-mm1. - Changes from

Hi Alasdair and all, This is the dm-ioband version 1.8.0 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. This release is a minor bug fix and confirmed running on the latest stable kernel 2.6.27.1. - Can be applied to the kernel 2.6.27.1 and 2.6.27-rc5-mm1. - Changes from

Hi Alasdair and all, This is the dm-ioband version 1.8.0 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. This release is a minor bug fix and confirmed running on the latest stable kernel 2.6.27.1. - Can be applied to the kernel 2.6.27.1 and 2.6.27-rc5-mm1. - Changes from