qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liu Yuan <namei.unix@gmail.com>
To: Abel Gordon <ABELG@il.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Eran Raichstein <ERANRA@il.ibm.com>,
	Avishay Traeger <AVISHAY@il.ibm.com>,
	Nadav Har'El <nyh@math.technion.ac.il>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Muli Ben-Yehuda <mulix@mulix.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Loic Dachary <loic@dachary.org>,
	Paolo Bonzini <pbonzini@redhat.com>, Asias He <asias@redhat.com>,
	Razya Ladelsky <RAZYA@il.ibm.com>
Subject: Re: [Qemu-devel] Block I/O optimizations
Date: Thu, 04 Apr 2013 21:41:28 +0800	[thread overview]
Message-ID: <515D8308.9070707@gmail.com> (raw)
In-Reply-To: <OF16170E7B.5F04B7FF-ONC2257B43.002D7871-C2257B43.002F4FED@il.ibm.com>

On 04/04/2013 04:36 PM, Abel Gordon wrote:
> We just posted a technical report that describes the design and evaluation
> of the work we did to improve virtual net/block I/O scalability and
> performance based on vhost and hosting multiple KVM guests.
> You can find the report here: http://goo.gl/RKppy
> 
> (full link:
> http://domino.research.ibm.com/library/cyberdig.nsf/1e4115aea78b6e7c85256b360066f0d4/479e3578ed05bfac85257b4200427735!OpenDocument&Highlight=0,h-0319
> )
> 
> I can present this work in the next QEMU community call.

Hi Abel,

   Could you share the presentation to me? I am very interested in your
works and I once have had done some works on vhost_blk. (I can't attend
community call)

Thanks,
Yuan

  parent reply	other threads:[~2013-04-04 13:41 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 [this message]
2013-03-13 15:21   ` Stefan Hajnoczi
2013-03-29 13:33     ` Loic Dachary

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=515D8308.9070707@gmail.com \
    --to=namei.unix@gmail.com \
    --cc=ABELG@il.ibm.com \
    --cc=AVISHAY@il.ibm.com \
    --cc=ERANRA@il.ibm.com \
    --cc=RAZYA@il.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=asias@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=loic@dachary.org \
    --cc=mst@redhat.com \
    --cc=mulix@mulix.org \
    --cc=nyh@math.technion.ac.il \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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).