qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: "Wangting (Kathy)" <kathy.wangting@huawei.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] question about vioscsi queue depth patch
Date: Tue, 09 Dec 2014 20:07:02 +1100	[thread overview]
Message-ID: <1418116022.9785.14.camel@oscar> (raw)
In-Reply-To: <5486B0E1.3090006@huawei.com>

On Tue, 2014-12-09 at 16:20 +0800, Wangting (Kathy) wrote:
> Hi Vadim,
> 
>     I test the vioscsi 0001-queue-depth254.patch for virtio-win-0.1-74 with minor modifications about
> 
> virtio api, because it have not updated to use the linux api. When a VM with four disks in one controller
> 
> and 4kb 32depth sequential read for each disk at the same time, the tool of iometer which simulates
> 
> the IO model become no response. If fit the patch into virtio-win-0.1-94, it works well.
> 
>     Is there some bug with the old virtio api, or is there some reason that the patch can not work normally
> 
> in virtio-win-0.1-74?
There were a lot of bug-fixes / changes introduced since build 74
(November 2013). Some of them did affect SRB completion and queue depth
logic.
So do you see any performance improvement after applying the patch?

Cheers,
Vadim.

> 
> 
> 
>     Best wishes,
> 
>     Ting Wang
> 
> 

      reply	other threads:[~2014-12-09  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30  6:54 [Qemu-devel] MSI interrupt support with vioscsi.c miniport driver Wangting (Kathy)
2014-10-30  8:48 ` Vadim Rozenfeld
2014-10-30 10:28   ` Wangting (Kathy)
2014-10-30 11:15     ` Vadim Rozenfeld
2014-10-31  1:55       ` Wangting (Kathy)
2014-12-09  8:20         ` [Qemu-devel] question about vioscsi queue depth patch Wangting (Kathy)
2014-12-09  9:07           ` Vadim Rozenfeld [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=1418116022.9785.14.camel@oscar \
    --to=vrozenfe@redhat.com \
    --cc=kathy.wangting@huawei.com \
    --cc=qemu-devel@nongnu.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).