From: Michael Baysek <mbaysek@liquidweb.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: vhost-blk development
Date: Tue, 10 Apr 2012 13:25:43 -0400 (EDT) [thread overview]
Message-ID: <24144665.60022.1334078743662.JavaMail.root@zimbra.liquidweb.com> (raw)
In-Reply-To: <CAJSP0QUp+EHcErj+Ls+jAMu+z21kU2iHSorGMcjEefr6YNt7_g@mail.gmail.com>
Hi Stefan.
Well, I'm trying to determine which I/O method currently has the very least performance overhead and gives the best performance for both reads and writes.
I am doing my testing by putting the entire guest onto a ramdisk. I'm working on an i5-760 with 16GB RAM with VT-d enabled. I am running the standard Centos 6 kernel with 0.12.1.2 release of qemu-kvm that comes stock on Centos 6. The guest is configured with 512 MB RAM, using, 4 cpu cores with it's /dev/vda being the ramdisk on the host.
I'm not closed to building a custom kernel or kvm if I can get better performance reliably. However, my initial attempts with the 3.3.1 kernel and latest kvm gave mixed results.
I've been using iozone 3.98 with -O -l32 -i0 -i1 -i2 -e -+n -r4K -s250M to measure performance.
So, I was interested in vhost-blk since it seemed like a promising avenue to take a look at. If you have any other thoughts, that would also be helpful.
-Mike
----- Original Message -----
From: "Stefan Hajnoczi" <stefanha@gmail.com>
To: "Michael Baysek" <mbaysek@liquidweb.com>
Cc: kvm@vger.kernel.org
Sent: Tuesday, April 10, 2012 4:55:26 AM
Subject: Re: vhost-blk development
On Mon, Apr 9, 2012 at 11:59 PM, Michael Baysek <mbaysek@liquidweb.com> wrote:
> Hi all. I'm interested in any developments on the vhost-blk in kernel accelerator for disk i/o.
>
> I had seen a patchset on LKML https://lkml.org/lkml/2011/7/28/175 but that is rather old. Are there any newer developments going on with the vhost-blk stuff?
Hi Michael,
I'm curious what you are looking for in vhost-blk. Are you trying to
improve disk performance for KVM guests?
Perhaps you'd like to share your configuration, workload, and other
details so that we can discuss how to improve performance.
Stefan
next prev parent reply other threads:[~2012-04-10 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 22:59 vhost-blk development Michael Baysek
2012-04-10 11:55 ` Stefan Hajnoczi
2012-04-10 17:25 ` Michael Baysek [this message]
2012-04-11 10:19 ` Stefan Hajnoczi
2012-04-11 16:52 ` Michael Baysek
2012-04-12 8:30 ` Stefan Hajnoczi
2012-04-13 5:38 ` Liu Yuan
2012-04-19 20:26 ` Michael Baysek
2012-04-20 4:28 ` Liu Yuan
2012-04-20 20:23 ` Michael Baysek
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=24144665.60022.1334078743662.JavaMail.root@zimbra.liquidweb.com \
--to=mbaysek@liquidweb.com \
--cc=kvm@vger.kernel.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.