similar to: No subject

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, 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 all, This is a new release of blkio-cgroup which provides an IO tracking mechanism. You can also download this series of patches from http://people.valinux.co.jp/~ryov/blkio-cgroup/ Changes from the previous release ================================= - bio-cgroup renamed to blkio-cgroup. - Use part of page_cgroup->flags to store the blkio-cgroup ID. This code is taken from Andrea's

Hi all, This is a new release of blkio-cgroup which provides an IO tracking mechanism. You can also download this series of patches from http://people.valinux.co.jp/~ryov/blkio-cgroup/ Changes from the previous release ================================= - bio-cgroup renamed to blkio-cgroup. - Use part of page_cgroup->flags to store the blkio-cgroup ID. This code is taken from Andrea's

Hi all, This is a new release of blkio-cgroup which provides an IO tracking mechanism. You can also download this series of patches from http://people.valinux.co.jp/~ryov/blkio-cgroup/ Changes from the previous release ================================= - bio-cgroup renamed to blkio-cgroup. - Use part of page_cgroup->flags to store the blkio-cgroup ID. This code is taken from Andrea's

independently, you should make each disk have its own cgroup subsystem, which only can be defined when compiling the kernel. This is impossible because every linux box has various number of disks. So you think it may be possible to make each cgroup have lots of control files for each device as a workaround. But it isn't allowed to add/remove control files when some devices are hot-added or

independently, you should make each disk have its own cgroup subsystem, which only can be defined when compiling the kernel. This is impossible because every linux box has various number of disks. So you think it may be possible to make each cgroup have lots of control files for each device as a workaround. But it isn't allowed to add/remove control files when some devices are hot-added or

should be passed to the I/O schedulers, since the maximum number of request descriptors is limited. And I still don't understand if you want to make your rb-tree work efficiently, you need to put a lot of bios or request descriptors into the tree. Is that what you are going to do? On the other hand, dm-ioband tries to minimize to have bios blocked. And I have a plan on reducing the maximum

should be passed to the I/O schedulers, since the maximum number of request descriptors is limited. And I still don't understand if you want to make your rb-tree work efficiently, you need to put a lot of bios or request descriptors into the tree. Is that what you are going to do? On the other hand, dm-ioband tries to minimize to have bios blocked. And I have a plan on reducing the maximum

Hi all, With this series of patches, you can determine the owners of any type of I/Os. I ported the previous version to linux-2.6.26-rc2-mm1. This makes dm-ioband -- I/O bandwidth controller -- be able to control the Block I/O bandwidths even when it accepts delayed write requests. Dm-ioband can find the owner cgroup of each request. It is also possible that OpenVz team and NEC Uchida-san team

Hi all, With this series of patches, you can determine the owners of any type of I/Os. I ported the previous version to linux-2.6.26-rc2-mm1. This makes dm-ioband -- I/O bandwidth controller -- be able to control the Block I/O bandwidths even when it accepts delayed write requests. Dm-ioband can find the owner cgroup of each request. It is also possible that OpenVz team and NEC Uchida-san team

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

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

and nice. My concern is "bio_cgroup_id". It's provided only for bio_cgroup. In this summer, I tried to add swap_cgroup_id only for mem+swap controller but commenters said "please provide "id and lookup" in cgroup layer, it should be useful." And I agree them. (and postponed it ;) Could you try "id" in cgroup layer ? How do you think, Paul and others ?

and nice. My concern is "bio_cgroup_id". It's provided only for bio_cgroup. In this summer, I tried to add swap_cgroup_id only for mem+swap controller but commenters said "please provide "id and lookup" in cgroup layer, it should be useful." And I agree them. (and postponed it ;) Could you try "id" in cgroup layer ? How do you think, Paul and others ?