From: Kenni Lund <kenni@kelu.dk>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: dlaor@redhat.com, Javier Guerra <javier@guerrag.com>,
Yan Vugenfirer <yvugenfi@redhat.com>,
kvm@vger.kernel.org
Subject: Re: Binary Windows guest drivers are released
Date: Fri, 25 Sep 2009 09:53:31 +0200 [thread overview]
Message-ID: <3b1f68ef0909250053v21634eb6o7bdbf856213ea716@mail.gmail.com> (raw)
In-Reply-To: <4ABC6896.5040805@redhat.com>
2009/9/25 Vadim Rozenfeld <vrozenfe@redhat.com>:
> On 09/25/2009 12:07 AM, Dor Laor wrote:
>>
>> On 09/24/2009 11:59 PM, Javier Guerra wrote:
>>>
>>> On Thu, Sep 24, 2009 at 3:38 PM, Kenni Lund<kenni@kelu.dk> wrote:
>>>>
>>>> I've done some benchmarking with the drivers on Windows XP SP3 32bit,
>>>> but it seems like using the VirtIO drivers are slower than the IDE
>>>> drivers in
>>>> (almost) all cases. Perhaps I've missed something or does the driver
>>>> still
>>>> need optimization?
>>>
>>> very interesting!
>>>
>>> it seems that IDE wins on all the performance numbers, but VirtIO
>>> always has lower CPU utilization. i guess this is guest CPU %, right?
>>> it would also be interesting to compare the CPU usage from the host
>>> point of view, since a lower 'off-guest' CPU usage is very important
>>> for scaling to many guests doing I/O.
>>>
>> These drivers are mainly tweaked for win2k3 and win2k8. We once had queue
>> depth settings in the driver, not sure we still have it, Vadim, can you add
>> more info?
>> Dor
>
> Windows XP 32-bit virtio block driver was created from our mainline code
> almost for fun.
> Not like our mainline code, which is STORPORT oriented, it is a SCSIPORT
> (!!!!) mini-port driver.
> SCSIPORT has never been known as I/O optimized storage stack.
> SCSIPORT architecture is almost dead officially.
> Windows XP 32-bit has no support for STORPORT or virtual storage stack.
Ok, in that case, wouldn't it be better simply not to build the XP driver and
instead put a note somewhere (in the wiki?), saying that it doesn't make
sense to use VirtIO on XP due to these reasons?
> Developing monolithic disk driver, which will sit right on top of virtio-blk
> PCI device, looks like the one way
> to have some kind of high throughput storage for Windows XP 32-bit.
Ok, since these drivers are targeted Windows Server and XP is getting old,
I suppose no efforts will be put into developing such driver, or?
Best Regards,
Kenni
next prev parent reply other threads:[~2009-09-25 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 13:13 Binary Windows guest drivers are released Yan Vugenfirer
2009-09-24 19:23 ` Glennie Vignarajah
2009-09-24 20:38 ` Kenni Lund
2009-09-24 20:59 ` Javier Guerra
2009-09-24 21:07 ` Dor Laor
2009-09-25 6:52 ` Vadim Rozenfeld
2009-09-25 7:53 ` Kenni Lund [this message]
2009-09-25 9:01 ` Vadim Rozenfeld
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=3b1f68ef0909250053v21634eb6o7bdbf856213ea716@mail.gmail.com \
--to=kenni@kelu.dk \
--cc=dlaor@redhat.com \
--cc=javier@guerrag.com \
--cc=kvm@vger.kernel.org \
--cc=vrozenfe@redhat.com \
--cc=yvugenfi@redhat.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;
as well as URLs for NNTP newsgroup(s).