similar to: No subject

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

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 ?

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 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

Hello all, I've implemented a block device which throttles block I/O bandwidth, which I called dm-ioband, and been trying to throttle I/O bandwidth on KVM environment. But unfortunately it doesn't work well, the number of issued I/Os is not according to the bandwidth setting. On the other hand, I got the good result when accessing directly to the local disk on the local machine. I'm

Hello all, I've implemented a block device which throttles block I/O bandwidth, which I called dm-ioband, and been trying to throttle I/O bandwidth on KVM environment. But unfortunately it doesn't work well, the number of issued I/Os is not according to the bandwidth setting. On the other hand, I got the good result when accessing directly to the local disk on the local machine. I'm

Hi all, This is a new release of blkio-cgroup v11. Changes: - The function cgroup_get_from_page() is added which determines to which cgroup a given page belongs. This function is introduced from Vivek's io-controller patch. Thanks Vivek. - Fix a type mismatch of the refcount of io_context. The refcount has been changed to atomic_long_t. This patch can be applied to 2.6.31-rc7. The

Hi all, I'm pleased to announce that the new dm-ioband RPM package (v1.12.0) has been released at: http://sourceforge.net/apps/trac/ioband/wiki/dm-ioband dm-ioband provides disk bandwidth control on per partition, per user, per process and per virtual machine (such as KVM or Xen) basis. The RPM packages are for Red Hat Enterprise Linux 5.x and CentOS 5.x. They were tested on RHEL 5.2 and

Hi all, I'm pleased to announce that the new dm-ioband RPM package (v1.12.0) has been released at: http://sourceforge.net/apps/trac/ioband/wiki/dm-ioband dm-ioband provides disk bandwidth control on per partition, per user, per process and per virtual machine (such as KVM or Xen) basis. The RPM packages are for Red Hat Enterprise Linux 5.x and CentOS 5.x. They were tested on RHEL 5.2 and

Hi all, I'm pleased to announce that the new dm-ioband RPM package (v1.12.0) has been released at: http://sourceforge.net/apps/trac/ioband/wiki/dm-ioband dm-ioband provides disk bandwidth control on per partition, per user, per process and per virtual machine (such as KVM or Xen) basis. The RPM packages are for Red Hat Enterprise Linux 5.x and CentOS 5.x. They were tested on RHEL 5.2 and

Hi all, This is a new release of blkio-cgroup v11. Changes: - The function cgroup_get_from_page() is added which determines to which cgroup a given page belongs. This function is introduced from Vivek's io-controller patch. Thanks Vivek. - Fix a type mismatch of the refcount of io_context. The refcount has been changed to atomic_long_t. This patch can be applied to 2.6.31-rc7. The

Hi all, This is a new release of blkio-cgroup v11. Changes: - The function cgroup_get_from_page() is added which determines to which cgroup a given page belongs. This function is introduced from Vivek's io-controller patch. Thanks Vivek. - Fix a type mismatch of the refcount of io_context. The refcount has been changed to atomic_long_t. This patch can be applied to 2.6.31-rc7. The

Hi all, This is a new release of blkio-cgroup v10. This release reduces IO tracking overhead and fixes an issue that could cause a deadlock since lock_page_cgroup() is no longer used. Thank you KAMEZAWA-san for your suggestions and pointing out the issue. This patch can be applied to 2.6.31-rc3-mmotm0716 and 2.6.31-rc4. The list of the patches: [PATCH 1/7] blkio-cgroup-v10: Introduction