On Fri, Jun 19, 2009 at 1:37 PM, Vivek Goyal<vgoyal@xxxxxxxxxx> wrote: > > You can use the following format to play with the new interface. > #echo DEV:weight:ioprio_class > /patch/to/cgroup/policy > weight=0 means removing the policy for DEV. > > Examples: > Configure weight=300 ioprio_class=2 on /dev/hdb in this cgroup > # echo /dev/hdb:300:2 > io.policy > # cat io.policy > dev weight class > /dev/hdb 300 2 I think that the read and write should be consistent. Can you just use white-space separation for both, rather than colon-separation for writes and white-space separation for reads? Also, storing device inode paths statically as strings into the io_policy structure seems wrong, since it's quite possible for the device node that was used originally to be gone by the time that someone reads the io.policy file, or renamed, or even replaced with an inode that refers to to a different block device My preferred alternatives would be: - read/write the value as a device number rather than a name - read/write the block device's actual name (e.g. hda or sda) rather than a path to the inode Paul -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
