qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Block I/O optimizations
Date: Fri, 29 Mar 2013 14:33:23 +0100	[thread overview]
Message-ID: <51559823.9090703@dachary.org> (raw)
In-Reply-To: <CAJSP0QWLNFTgZye8gJ+D0fOj6iYNdTxMPR0+sUd80RxbDVpfsQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

Hi Stefan,

This is excellent ! Thank you very much :-)

Cheers

On 03/13/2013 04:21 PM, Stefan Hajnoczi wrote:
> On Thu, Feb 21, 2013 at 9:11 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> On Mon, Feb 18, 2013 at 7:19 PM, Loic Dachary <loic@dachary.org> wrote:
>>> I recently tried to figure out the best and easiest ways to increase block I/O performances with qemu. Not being a qemu expert, I expected to find a few optimization tricks. Much to my surprise, it appears that there are many significant improvements being worked on. This is excellent news :-)
>>>
>>> However, I'm not sure I understand how they all fit together. It's probably quite obvious from the developer point of view but I would very much appreciate an overview of how dataplane, vhost-blk, ELVIS etc. should be used or developed to maximize I/O performances. Are there documents I should read ? If not, would someone be willing to share bits of wisdom ?
>>
>> Hi Loic,
>> There will be more information on dataplane shortly.  I'll write up a
>> blog post and share the link with you.
> 
> Hi Loic,
> Here is an overview of virtio-blk data plane and how to use it:
> http://blog.vmsplice.net/2013/03/new-in-qemu-14-high-performance-virtio.html
> 
> Stefan
> 
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2013-03-29 13:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <512270C4.3090401@dachary.org>
     [not found] ` <CAJSP0QWOzRLi=QPtS8uLR9_c1=M9ptjx+rd8fg2Mnj6tjXAOQA@mail.gmail.com>
     [not found]   ` <OFB9942FE4.54D170F3-ONC2257B1D.002BE3C8-C2257B1D.00306994@il.ibm.com>
     [not found]     ` <20130225125056.GB3202@stefanha-thinkpad.redhat.com>
     [not found]       ` <OFDEF91A17.56D72381-ONC2257B1D.0061DD03-C2257B1D.00671633@il.ibm.com>
     [not found]         ` <20130226164530.GF8662@stefanha-thinkpad.redhat.com>
     [not found]           ` <OF97530B15.2137222C-ONC2257B1F.004F1393-C2257B1F.0054C2F9@il.ibm.com>
     [not found]             ` <20130228144304.GC18389@stefanha-thinkpad.redhat.com>
     [not found]               ` <OF89B4E81E.00226F20-ONC2257B20.00574B6E-C2257B20.0064B893@il.ibm.com>
2013-03-01 10:54                 ` [Qemu-devel] Block I/O optimizations Stefan Hajnoczi
2013-03-03  9:35                   ` Abel Gordon
2013-03-04  8:45                     ` Stefan Hajnoczi
2013-03-04 11:10                     ` Michael S. Tsirkin
2013-04-04  8:36                     ` Abel Gordon
2013-04-04 13:08                       ` Anthony Liguori
2013-04-04 13:41                       ` Liu Yuan
2013-03-13 15:21   ` Stefan Hajnoczi
2013-03-29 13:33     ` Loic Dachary [this message]

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=51559823.9090703@dachary.org \
    --to=loic@dachary.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).