On Mon, Nov 29, 2010 at 4:58 AM, Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote: > On Mon, Nov 29, 2010 at 2:00 AM, T Johnson <tjohnson46@xxxxxxxxx> wrote: >> Hello, >> >> On Thu, Nov 25, 2010 at 3:33 AM, Nikola Ciprich <extmaillist@xxxxxxxxxxx> wrote: >>> Hello Thomas, >>> I t hink blkio-cgroup really can't help You here, but since NFS is >>> network protocol, >>> why not just consider some kind of network shaping? >>> n. >> >> I thought about this, but it's rather imprecise I imagine if I try to >> limit the number of packets per second and hope that matches reads or >> writes per second. Secondly, I have many guests running to the same >> NFS server which makes limiting per kvm guest somewhat impossible when >> the network tools I know if would limit per NFS server. > > Perhaps iptables/tc can mark the stream based on the client process > ID? Each VM has a qemu-kvm userspace process that will issue file > I/O. Someone with more networking knowledge could confirm whether or > not it is possible to mark based on the process ID using the in-kernel > NFS client. > > You don't need to limit based on packets per second. You can do > bandwidth-based traffic shaping with tc. Thanks. That is an interesting idea. As far as packets or bandwidth, my thought was IOPS were more expensive than total bytes transferred.. so I would want to limit the number of distinct read/write requests if possible. Anyway, I'm surprised this doesn't seem to come up more often. If anyone out there is listening, please consider this a plea for something built in to limit i/o in this situation. It would be extremely useful. Thanks again -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
