similar to: [PATCH 0/3] ADD Virtual Block Device requests information.

This patch make xentop output statistics about both blkback and blktap. And, xentop also display back-end driver type in detail view mode. # HG changeset patch # User s-uchida@ap.jp.nec.com # Date 1180665749 -32400 # Node ID 1b36d6f6c7a98728382de93ee23c8c97b0b95dbd # Parent 1768a89bb87824249827d935d7803d8193bdeb05 XENTOP: Displaying blktap information. Signed-off-by: Satoshi UCHIDA

Hi. These patches add the output function for blktap statistics into xentop. Currently, xentop outputs only blkback statistics, and not blktap statistics. By these patches, xentop is made cover both blkback and blktap. In xen, back-end driver has two types; blkback and blktap. Blkback driver is old back-end driver. Blktap driver is new back-end driver and is recommended currently. Usage of both

I sent before few days. However, anyone did not comments. So, I resend this patch series. I hope to response for this patch series. This patch series provides the function to display VBD information through xentop. VBD information will be possible to get through sysfs which is locale in /sys/devices/xen-backed/vbd-x-xxxx, by previous patch. In this patch series, libxenstat collects these

This patch series provides the function to display VBD information through xentop. VBD information will be possible to get through sysfs which is locale in /sys/devices/xen-backed/vbd-x-xxxx, by previous patch. In this patch series, libxenstat collects these information and xentop display tem. The change from ver.1 is only libxenstat in order to handle sysfs information. I appreciate any

This patch provides a I/O request management framework. This framework can control virtual block device threads at 7 places : * deciding that virtual block devices(threads) is ether going or waiting, * before allocating pending_request variables, * after allocated pending_request variables, * after allocated no pending_request variables (Namely, out of request), * after freed

This patch add a interface for parameter of cfq driver data. Signed-off-by: Satoshi UCHIDA <s-uchida at ap.jp.nec.com> --- block/cfq-cgroup.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++- 1 files changed, 58 insertions(+), 1 deletions(-) diff --git a/block/cfq-cgroup.c b/block/cfq-cgroup.c index 4938fa0..776874d 100644 --- a/block/cfq-cgroup.c +++

This patch introcude cfq_cgroup structure which is type for group control within expanded CFQ scheduler. In addition, the cfq_cgroup structure has "ioprio" entry which is preference of group for I/O. Signed-off-by: Satoshi UCHIDA <s-uchida at ap.jp.nec.com> --- block/cfq-cgroup.c | 148 +++++++++++++++++++++++++++++++++++++++++

# HG changeset patch # User john.levon@sun.com # Date 1172534164 28800 # Node ID 37fce3c0c10baee370ecc39b6a50fed8b232bd69 # Parent 4998793aa87729fbe8a582faa3a22c9ecfefe13c Fix for Solaris compile/output for VBDs in xentop. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/xenstat/xentop/xentop.c b/tools/xenstat/xentop/xentop.c --- a/tools/xenstat/xentop/xentop.c +++

Hi all, Now I use xentop to get disk statistical information. NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR VBD_RSECT VBD_WSECT SSID Domain-0 -----r 96233 0.7 3902464 23.3 no limit n/a 12 0 0 0 0 0 0 0 0 0 0 slave3

This patch introduces iprio class for cfq data control layer. By applying this patch, controller can also handle the RT/IDLE properties among groups. Signed-off-by: Satoshi UCHIDA <s-uchida at ap.jp.nec.com> --- block/cfq-cgroup.c | 344 +++++++++++++++++++++++++------------------ include/linux/cfq-iosched.h | 1 + 2 files changed, 203 insertions(+), 142 deletions(-)

This patch introduces iprio class for cfq data control layer. By applying this patch, controller can also handle the RT/IDLE properties among groups. Signed-off-by: Satoshi UCHIDA <s-uchida at ap.jp.nec.com> --- block/cfq-cgroup.c | 344 +++++++++++++++++++++++++------------------ include/linux/cfq-iosched.h | 1 + 2 files changed, 203 insertions(+), 142 deletions(-)

All, I have a domU running Ubuntu 12.04.1 LTS 64bit using PVonHVM which is working well but I noticed a quirk and just wanted to check it wasn''t just my misunderstanding. On my dom0 (Arch Linux, 64bit, AMD Phenom 2 X4 965 CPU, Xen 4.2.0 from my own PKGBUILD) I run "xl top" and xentop loads and shows all the currently running domains; only none of the domains have anything

Hi, I''m new to Xen and I''ve set up a few domUs using Debian (I suspect there may be a problem there, see at end). To begin with everything worked OK, I rebooted domUs without any problems, but twice now when I try when I try to restart or shutdown a domain, the xm command locks up. # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information

This patch is cleaning code in xenbus.c by VBD_SHOW macro. VBD_SHOW macro can be applied show functions with corresponded to ''physical_devices'' and ''mode'' attributes. And corresponding ''device_create_file'' and ''device_remove_file'' function can be inserted into ''xenvbd_sysfs_addif'' and

Hi Is there a place where I can get explaination for VBD and N/W related stats produced by xentop ? Or if some one knows.. can they please reply to this email. Thanks in advance. -nb _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, One of our colleagues spotted a problem in xentop. Sometimes the VBD_WSECT value suddenly becomes unreasonably high, and it turned out xentop reads /sys/bus/xen-backend/devices/vbd-(domid)-(devID)/statistics/wr_sect into an unsigned long long. That value is exposed by blkback, and among other stat counters, it''s a signed integer: drivers/block/xen-blkback/common.h struct

Hi All, I''m a beginner in Xen. Recently I''ve configured one VM (vm03) hosted in my physical machine. I ran the "netperf" workload in the vm01, and used the "top" command in the vm03 to test the behavior of the running workload. Meanwhile, I also used the "xentop" command in domain0 to see the resource consumption in vm03. Interestingly, I found that

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

Xentop encounters error in pv-ops domain0, because the VBD path in sysfs changes to "/sys/devices" Also delete the macro in xenstat_netbsd.c, because it is not used. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Best Regards, -- Dongxiao _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi all, On xen platform, the output of xentop tool is like this: NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k)VBDS VBD_OO VBD_RD VBD_WR VBD_RSECT VBD_WSECT SSID Domain-0 -----r 96025 0.0 3902464 23.3 no limit n/a 12 0 0 0 0 0 0 0 0 0 0 slave3