On Tue, May 31, 2011 at 03:55:49PM -0400, Vivek Goyal wrote: >Date: Tue, 31 May 2011 15:55:49 -0400 >From: Vivek Goyal <[email protected]> >To: Zhi Yong Wu <[email protected]> >Cc: [email protected], [email protected], [email protected], > [email protected], [email protected], > [email protected], [email protected], > [email protected], [email protected], [email protected], > [email protected], [email protected], [email protected] >Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits >User-Agent: Mutt/1.5.21 (2010-09-15) > >On Mon, May 30, 2011 at 01:09:23PM +0800, Zhi Yong Wu wrote: > >[..] >> 3.) How the users enable and play with it >> QEMU -drive option will be extended so that disk I/O limits can be >> specified on its command line, such as -drive [iops=xxx,][throughput=xxx] or >> -drive [iops_rd=xxx,][iops_wr=xxx,][throughput=xxx] etc. When this argument >> is specified, it means that "disk I/O limits" feature is enabled for this >> drive disk. > >How does throughput interface look like? is it bytes per second or something >else? Given your suggestion, its form will look like below:
-drive [iops=xxx][,bps=xxx] or -drive [iops_rd=xxx][,iops_wr=xxx][,bps_rd=xxx][,bps_wr=xxx] Regards, Zhiyong Wu > >Do we have read and write variants for throughput as we have for iops. > >if you have bytes interface(as kenrel does), then "bps_rd" and "bps_wr" >might be good names too for thoughput interface. > >Thanks >Vivek > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
