From: Jason Wang <jasowang@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org,
mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH RFC V2 4/4] tools: virtio: add a top-like utility for displaying vhost satistics
Date: Fri, 11 Apr 2014 11:04:51 +0800 [thread overview]
Message-ID: <1397185491.6230.4.camel@localhost> (raw)
In-Reply-To: <20140410092702.GJ22890@T430.nay.redhat.com>
On Thu, 2014-04-10 at 17:27 +0800, Fam Zheng wrote:
> On Fri, 03/21 17:41, Jason Wang wrote:
> > This patch adds simple python to display vhost satistics of vhost, the codes
> > were based on kvm_stat script from qemu. As work function has been recored,
> > filters could be used to distinguish which kinds of work are being executed or
> > queued:
> >
> > vhost statistics
> >
> > vhost_virtio_update_used_idx 1215215 0
> > vhost_virtio_get_vq_desc 1215215 0
> > vhost_work_queue_wakeup 986808 0
> > vhost_virtio_signal 811601 0
> > vhost_net_tx 611457 0
> > vhost_net_rx 603758 0
> > vhost_net_tx(datacopy) 601903 0
> > vhost_work_queue_wakeup(rx_net) 565081 0
> > vhost_virtio_signal(rx) 461603 0
> > vhost_work_queue_wakeup(tx_kick) 421718 0
> > vhost_virtio_update_avail_event 417346 0
> > vhost_virtio_signal(tx) 349998 0
> > vhost_work_queue_coalesce 39384 0
> > vhost_work_queue_coalesce(rx_net) 38677 0
> > vhost_net_tx(zerocopy) 9554 0
> > vhost_work_queue_coalesce(tx_kick) 707 0
> > vhost_work_queue_wakeup(rx_kick) 9 0
> >
> > Signed-off-by: Jason Wang <jasowang@redhat.com>
> > ---
> > tools/virtio/vhost_stat | 375 ++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 375 insertions(+)
> > create mode 100755 tools/virtio/vhost_stat
> >
> > diff --git a/tools/virtio/vhost_stat b/tools/virtio/vhost_stat
> > new file mode 100755
> > index 0000000..398fd4a
> > --- /dev/null
> > +++ b/tools/virtio/vhost_stat
> > @@ -0,0 +1,375 @@
> > +#!/usr/bin/python
> > +#
> > +# top-like utility for displaying vhost statistics
> > +#
> > +# Copyright 2012 Red Hat, Inc.
>
> Should it be 2014?
>
> Fam
>
> <snip>
Yes it should, thanks for pointing this out.
prev parent reply other threads:[~2014-04-11 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 9:41 [PATCH RFC V2 0/4] Adding tracepoints to vhost/net Jason Wang
2014-03-21 9:41 ` [PATCH RFC V2 1/4] vhost: introduce queue_index for tracing Jason Wang
2014-03-21 9:41 ` [PATCH RFC V2 2/4] vhost: basic tracepoints Jason Wang
2014-03-21 9:41 ` [PATCH RFC V2 3/4] vhost_net: add basic tracepoints for vhost_net Jason Wang
2014-03-21 9:41 ` [PATCH RFC V2 4/4] tools: virtio: add a top-like utility for displaying vhost satistics Jason Wang
[not found] ` <1395394913-19548-5-git-send-email-jasowang@redhat.com>
2014-04-10 9:27 ` Fam Zheng
[not found] ` <20140410092702.GJ22890@T430.nay.redhat.com>
2014-04-11 3:04 ` Jason Wang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1397185491.6230.4.camel@localhost \
--to=jasowang@redhat.com \
--cc=famz@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).