From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for Mar 30
Date: Tue, 30 Mar 2010 08:01:07 -0700 [thread overview]
Message-ID: <20100330150107.GI11934@x200.localdomain> (raw)
vhost-blk
- started w/ vhost-net, nice and modular
- qemu merging requests, so outperforming (throughput) for sequential write
- random read/write and sequential reads are comparable or better
- can't do e.g. qcow2
- spreading work across all cpu workqueues
- are there cases where we expect vhost-blk is needed?
- not driven by poor perf benchmarks, more driven from interest/curiosity
- hch's numbers (esp. large request) are solid
- low hanging fruit...no interrupt mitigation, addr lookup on all request
- get some performance numbers and profiles to see what we can do to
improve existing virtio before moving to vhost
qemu optimizations (re: above addr lookup)
- no long lived ptr to guest memory
- ram memory patch allowed for stable mapping
- objection was memory hotplug/remove
- how much do we want to gate qemu progress on memory hotplug?
- http://wiki.qemu.org/Features/RamAPI
ide emulation
- qemu virtio-blk vs. other hv ide emulation...ide was better
- this was some time ago
- older qemu, even qemu ide emulation was better than virtio-blk in
some cases
- ide still bounce buffering, and has some fundamental limitations
(some of those may be fixable w/ ahci)
- anyone looked at this recently?
reply other threads:[~2010-03-30 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100330150107.GI11934@x200.localdomain \
--to=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--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).