virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Asias He <asias@redhat.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: [PATCH v2 0/3] Improve virtio-blk performance
Date: Mon, 18 Jun 2012 14:53:07 +0800	[thread overview]
Message-ID: <1340002390-3950-1-git-send-email-asias@redhat.com> (raw)

This patchset implements bio-based IO path for virito-blk to improve
performance.

Fio test shows it gives, 28%, 24%, 21%, 16% IOPS boost and 32%, 17%, 21%, 16%
latency improvement for sequential read/write, random read/write respectively.

Asias He (3):
  block: Introduce __blk_segment_map_sg() helper
  block: Add blk_bio_map_sg() helper
  virtio-blk: Add bio-based IO path for virtio-blk

 block/blk-merge.c          |  117 +++++++++++++++++--------
 drivers/block/virtio_blk.c |  203 +++++++++++++++++++++++++++++++++++---------
 include/linux/blkdev.h     |    2 +
 3 files changed, 247 insertions(+), 75 deletions(-)

-- 
1.7.10.2

             reply	other threads:[~2012-06-18  6:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  6:53 Asias He [this message]
2012-06-18  6:53 ` [PATCH 1/3] block: Introduce __blk_segment_map_sg() helper Asias He
2012-06-18 21:31   ` Tejun Heo
2012-06-19  2:02     ` Asias He
2012-06-19 18:00       ` Tejun Heo
2012-06-18  6:53 ` [PATCH v2 2/3] block: Add blk_bio_map_sg() helper Asias He
2012-06-18  6:53 ` [PATCH 3/3] virtio-blk: Add bio-based IO path for virtio-blk Asias He
2012-06-18  7:46   ` Rusty Russell
2012-06-18  8:03     ` Asias He
2012-06-18 10:05       ` Rusty Russell
2012-06-18 11:14         ` Dor Laor
2012-06-18 11:39           ` Sasha Levin
2012-06-19  2:51             ` Asias He
2012-06-19  6:21               ` Dor Laor
2012-06-20  4:46                 ` Asias He
2012-06-21  9:49                   ` Dor Laor
2012-07-01 23:54               ` Rusty Russell
     [not found]               ` <87r4svxcjw.fsf@rustcorp.com.au>
2012-07-02  2:45                 ` Asias He
2012-07-02  6:41                   ` Rusty Russell
2012-07-03  0:39                     ` Asias He
2012-07-04  2:40                       ` Rusty Russell
2012-07-06  1:03                         ` Asias He
2012-07-03 13:31                     ` Paolo Bonzini
     [not found]                     ` <4FF2F417.2010209@redhat.com>
2012-07-03 14:02                       ` Asias He
2012-07-03 14:22           ` Ronen Hod
2012-07-03 14:28             ` Dor Laor
2012-07-04 14:10               ` Paolo Bonzini
2012-06-18 21:28         ` Tejun Heo
2012-06-19  2:39         ` Asias He
2012-06-18 10:13       ` Michael S. Tsirkin
2012-06-19  2:21         ` Asias He
2012-06-18  9:37   ` Stefan Hajnoczi
2012-06-18 10:21   ` Michael S. Tsirkin
2012-06-18 10:45     ` Stefan Hajnoczi
2012-06-19  2:30     ` Asias He
2012-06-18  9:14 ` [PATCH v2 0/3] Improve virtio-blk performance Stefan Hajnoczi
2012-06-18  9:39   ` Asias He
2012-06-18 10:58     ` Stefan Hajnoczi
2012-06-19  4:24       ` Asias He
2012-06-19 10:14         ` Stefan Hajnoczi

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=1340002390-3950-1-git-send-email-asias@redhat.com \
    --to=asias@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).