From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: KVM call minutes for May 25
Date: Tue, 25 May 2010 07:59:48 -0700 [thread overview]
Message-ID: <20100525145948.GC29293@x200.localdomain> (raw)
Generic Asynchronous task offloading
- keep vcpu thread from blocking
- generic approach is useful, comes down to specifics
- e.g. what is done in worker threads, how locking is handled
- offload blocking work to worker threads
- need to make device model reentrant
- can be simple w/ lock per device, but needs finer grained to be perfromant
- but needs
- thread pool should be relatively easy to merge
- two alternatives for virtfs
- one full request in thread, one that does syscalls asynchronously
- need to have something demonstrably better to make threading acceptable
- complexity of state machine vs. locking
- performance difference at the end (e.g. coarse grained locking
doesn't fully allow for parallel execution)
- lapic needs to be reentrant
- in qemu lapic should show off the benefit very well
- hpet would also benefit from being threaded
- multiple threads per device (needs device specific locking)
- qxl, scsi, virtfs...
- push global lock down to pio/mmio dispatch
- audit for global qemu state changes done w/in device
- anthony will set up wiki page to describe making device models reentrant
- looking for volunteers!
reply other threads:[~2010-05-25 14:59 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=20100525145948.GC29293@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