public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>, kvm@vger.kernel.org
Subject: Re: [RFC] vhost-blk implementation
Date: Mon, 29 Mar 2010 11:20:10 -0700	[thread overview]
Message-ID: <20100329182010.GM1744@sequoia.sous-sol.org> (raw)
In-Reply-To: <1269877312.7931.93.camel@badari-desktop>

* Badari Pulavarty (pbadari@us.ibm.com) wrote:
> I modified my vhost-blk implementation to offload work to
> work_queues instead of doing synchronously. Infact, I tried
> to spread the work across all the CPUs. But to my surprise,
> this did not improve the performance compared to virtio-blk.
> 
> I see vhost-blk taking more interrupts and context switches
> compared to virtio-blk. What is virtio-blk doing which I
> am not able to from vhost-blk ???

Your io wait time is twice as long and your throughput is about half.
I think the qmeu block submission does an extra attempt at merging
requests.  Does blktrace tell you anything interesting?

> procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----
>  r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
>  3  1   8920  56076  20760 5603556    0  104   196 79826 17164 13912  0  5 65 30  0
>  2  4   9488  57216  20744 5605616    0  114   195 81120 17397 13824  0  5 65 30  0
>  2  2  10028  68476  20728 5594764    0  108   206 80318 17162 13845  0  5 65 30  0
>  0  4  10560  70856  20708 5593088    0  106   205 82363 17402 13904  0  5 65 30  0
>  1  3  10948  80380  20672 5584452    0   78   178 79714 17113 13875  0  5 66 29  0
> 
> qemu virtio-blk:
> 
> procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----
>  r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
>  0  1  14124  57456   5144 4924060    0    0   139 142546 11287 9312  1  4 80 15  0
>  0  2  14124  56736   5148 4927396    0    0   146 142968 11283 9248  1  4 80 15  0
>  0  1  14124  56712   5384 4927020    0    0    74 150738 11182 9327  1  4 80 16  0
>  1  1  14124  55496   5392 4927904    0    0     2 159902 11172 9401  1  3 79 17  0
>  0  1  14124  55968   5408 4927232    0    0     0 159202 11212 9325  1  3 80 16  0

  reply	other threads:[~2010-03-29 18:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23  1:00 [RFC] vhost-blk implementation Badari Pulavarty
2010-03-23  1:16 ` Anthony Liguori
2010-03-23  1:45   ` Badari Pulavarty
2010-03-23  2:00     ` Anthony Liguori
2010-03-23  2:50       ` Badari Pulavarty
2010-03-23 10:05         ` Avi Kivity
2010-03-23 14:48           ` Badari Pulavarty
2010-03-23 10:03 ` Avi Kivity
2010-03-23 14:55   ` Badari Pulavarty
2010-03-23 16:53     ` Avi Kivity
2010-03-24 20:05   ` Christoph Hellwig
2010-03-25  6:29     ` Avi Kivity
2010-03-25 15:48       ` Christoph Hellwig
2010-03-25 15:51         ` Avi Kivity
2010-03-25 15:00     ` Asdo
2010-04-05 19:59       ` Christoph Hellwig
2010-04-07  0:36         ` [RFC] vhost-blk implementation (v2) Badari Pulavarty
2010-03-23 10:09 ` [RFC] vhost-blk implementation Eran Rom
2010-03-24 20:04 ` Christoph Hellwig
2010-03-24 20:22   ` Badari Pulavarty
2010-03-25  7:57     ` Avi Kivity
2010-03-25 14:36       ` Badari Pulavarty
2010-03-25 15:57     ` Christoph Hellwig
2010-03-26 18:53       ` Eran Rom
2010-04-08 16:17         ` Stefan Hajnoczi
2010-04-05 19:23     ` Christoph Hellwig
2010-04-05 23:17       ` Badari Pulavarty
2010-03-24 20:27   ` Badari Pulavarty
2010-03-29 15:41   ` Badari Pulavarty
2010-03-29 18:20     ` Chris Wright [this message]
2010-03-29 20:37       ` Avi Kivity
2010-03-29 22:51         ` Badari Pulavarty
2010-03-29 23:56           ` Chris Wright
2010-03-30 12:43           ` Avi Kivity
2010-04-05 14:22     ` Stefan Hajnoczi
2010-04-06  2:27       ` Badari Pulavarty

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=20100329182010.GM1744@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    /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