From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes June 29
Date: Tue, 03 Jul 2012 12:18:45 +0200 [thread overview]
Message-ID: <87fw99uoze.fsf@elfo.mitica> (raw)
Isaku reminds me that I forgot to pust that minutes:
2012-06-19
----------
- migration
* xbrle: ok
* huge memory: needs migration-thread, but should be ok
* postcopy: ask for latency: maximum/avg/std deviation
ask for vcpu utilization
RDMA?
* xbrle don't fix all the problems (vinod)
* Freeze is August 1st
* They asked for better numbers, at least:
* vcpu utilization (in percentange, Avi)
* latency of page faults over the network (Anthony)
* I can integrate your refactorings (postfix) for 1.2 (I have no problems with
them, 19 1st patches or so, but that is up-to-you and the others).
- multithreading vhost
* vhost has a lot of challenges with lots of small packets.
* use a couple of threads by device, one for reception and another for
sending (Anthony)
* two problems to address (NUMA locality), and scalability (mst)
(Anthony has better notes of the last part).
Note that I am holidays this week (July 2th), so expect lags on my email response.
Later, Juan.
reply other threads:[~2012-07-03 10:19 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=87fw99uoze.fsf@elfo.mitica \
--to=quintela@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).