similar to: [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview

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

I am racking my brain over this, probably because I only know very simple mysql functions. Basically I''ve got a few tables, ex: Albums (id,name,band_id); Bands (id,name,label_id), and Label (id,name) I want to search through both album.name, band.name, and label.name throwing all results into a variable, with no redundant info. I think what I need to be doing is setting up some

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

Shuji, I suspect that bruto blows up because your data are linearly separable. To see this (if you didn't already know), try library(lattice) splom(~x, groups = y) and look at the first row. If you are trying to do classification, there are a few methods that would choke on this (logistic regression) and a few that won't (trees, svms etc). I would guess that bruto is in the latter

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 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 everyone, This is dm-ioband version 1.0.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. - Can be applied to the kernel 2.6.26-rc2-mm1. - Changes from 0.0.4 (24th April): - Performance tuning - A new bandwidth control policy is added. This policy controls

Hi everyone, This is dm-ioband version 1.0.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. - Can be applied to the kernel 2.6.26-rc2-mm1. - Changes from 0.0.4 (24th April): - Performance tuning - A new bandwidth control policy is added. This policy controls

Hi everyone, This is dm-ioband version 1.0.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. - Can be applied to the kernel 2.6.26-rc2-mm1. - Changes from 0.0.4 (24th April): - Performance tuning - A new bandwidth control policy is added. This policy controls