search for: rd_sect

...s sufficient to distinguish VBD types. Therefore, it is better to remove the prefix "tap_" in sysfs entries of blktap. For example, currently sysfs entries are named as follows. [root@xenmachine1 ~]# ls /sys/devices/xen-backend/vbd-1-51712/statistics/ br_req oo_req rd_req rd_sect wr_req wr_sect [root@xenmachine1 ~]# ls /sys/devices/xen-backend/tap-2-51712/statistics/ tap_oo_req tap_rd_req tap_rd_sect tap_wr_req tap_wr_sect After applying these patches, names of sysfs entries are changed as follows. [root@xenmachine1 ~]# ls /sys/devices/xen-backend/vb...

...1048576 6.3 2097152 12.5 2 1 1573 8 2 0 2433 6688 109973 88770 0 For the red part, I need to change the size to MB or KB. Just now, I check the xentop code, xentop gets the related information from /sys/devices/vbd-29-51713/statistics/rd_sect or /sys/devices/vbd-29-51713/statistics/wr_sect files. I do not know how to change these number to MB or KB. Does anybody know how to do that? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Just moving a chunk of files from one filesysstem on xvba to another on xvdb, and was monitoring with xentop as it was taking longer than expected. The VBD_RD and VBD_WR counters were both clocking-up as expected, as was the VBD_RSECT counter, but the VBD_WSECT counter was stuck on zero, I toggled on the individual VBD device counters and these showed the same (with the RD and WR counters

Just moving a chunk of files from one filesysstem on xvba to another on xvdb, and was monitoring with xentop as it was taking longer than expected. The VBD_RD and VBD_WR counters were both clocking-up as expected, as was the VBD_RSECT counter, but the VBD_WSECT counter was stuck on zero, I toggled on the individual VBD device counters and these showed the same (with the RD and WR counters

Dear list, This is the V4 of the trim support for xen-blkfront/blkback, Now we move BLKIF_OP_TRIM to BLKIF_OP_DISCARD, and dropped all "trim" stuffs in the patches, and use "discard" instead. Also we updated the helpers of blkif_x86_{32|64}_request or we will meet problems using a non-native protocol. And this patch has been tested with both SSD and raw file, with SSD we will