linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Oliver Chick <oliver.chick@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] Persistent grant maps for xen blk drivers
Date: Thu, 20 Sep 2012 13:09:43 +0300	[thread overview]
Message-ID: <20120920100943.GX8912@reaktio.net> (raw)
In-Reply-To: <1348133733.24539.8.camel@oliverchick-Precision-WorkStation-T3400>

On Thu, Sep 20, 2012 at 10:35:33AM +0100, Oliver Chick wrote:
> I have attached a graph that shows the results of my benchmarking.
> 
> The setup is:
> -Xeon X5650
> -32GB of Ram
> -Xen 4.2
> -Linux 3.5.0 for dom0 and domus
> -Dom0 has 24 CPUs.
> -Each guest has a (separate) xvdb backed by a 1GB ramdisk (/dev/ramX) in
> dom0. No LVM on these.
> -The setup is that initially 1 guest does an fio sequential read of the
> ramdisk, then 2, then 3 etc.
> -The y axis is the sum of the iops, as reported by the guests' fio
> output.
> 

Thanks! The graph looks pretty nice :)

-- Pasi

> On Wed, 2012-09-19 at 14:16 +0100, X5650Pasi Kärkkäinen wrote:
> > On Wed, Sep 19, 2012 at 11:51:27AM +0100, Oliver Chick wrote:
> > > This patch implements persistent grants for the xen-blk{front,back}
> > > mechanism. The effect of this change is to reduce the number of unmap
> > > operations performed, since they cause a (costly) TLB shootdown. This
> > > allows the I/O performance to scale better when a large number of VMs
> > > are performing I/O.
> > > 
> > > Previously, the blkfront driver was supplied a bvec[] from the request
> > > queue. This was granted to dom0; dom0 performed the I/O and wrote
> > > directly into the grant-mapped memory and unmapped it; blkfront then
> > > removed foreign access for that grant. The cost of unmapping scales
> > > badly with the number of CPUs in Dom0. An experiment showed that when
> > > Dom0 has 24 VCPUs, and guests are performing parallel I/O to a
> > > ramdisk, the IPIs from performing unmap's is a bottleneck at 5 guests
> > > (at which point 650,000 IOPS are being performed in total). If more
> > > than 5 guests are used, the performance declines. By 10 guests, only
> > > 400,000 IOPS are being performed.
> > > 
> > > This patch improves performance by only unmapping when the connection
> > > between blkfront and back is broken.
> > >
> > 
> > So how many IOPS can you get with this patch / persistent grants ? 
> > 
> > -- Pasi
> > 
> 



  reply	other threads:[~2012-09-20 10:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 10:51 [PATCH] Persistent grant maps for xen blk drivers Oliver Chick
2012-09-19 11:17 ` Konrad Rzeszutek Wilk
2012-09-19 12:03 ` [Xen-devel] " Jan Beulich
2012-09-20  8:51   ` Oliver Chick
2012-09-20  9:11     ` Jan Beulich
2012-09-19 13:16 ` Pasi Kärkkäinen
2012-09-20  9:35   ` Oliver Chick
2012-09-20 10:09     ` Pasi Kärkkäinen [this message]
2012-09-19 14:11 ` Konrad Rzeszutek Wilk
2012-09-20 13:12   ` Oliver Chick
2012-09-20 13:52     ` Konrad Rzeszutek Wilk
2012-09-20 10:34 ` [Xen-devel] " David Vrabel
2012-09-20 11:30   ` Oliver Chick
2012-09-20 11:48     ` Jan Beulich
2012-09-20 13:49       ` Konrad Rzeszutek Wilk
2012-09-20 14:13         ` Oliver Chick
2012-09-20 16:10           ` Jan Beulich
2012-09-20 21:24           ` Konrad Rzeszutek Wilk
2012-09-21  7:18             ` Jan Beulich
2012-09-21  8:41               ` Oliver Chick
2012-09-21  9:41                 ` Jan Beulich
2012-09-21  8:10             ` Ian Campbell
2012-09-21 14:26               ` Konrad Rzeszutek Wilk
2012-09-20 15:35         ` Jan Beulich
2012-09-21 12:23       ` David Vrabel
2012-09-21 14:27         ` Konrad Rzeszutek Wilk
2012-09-21 16:17           ` David Vrabel
2012-09-21 17:13             ` Konrad Rzeszutek Wilk

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=20120920100943.GX8912@reaktio.net \
    --to=pasik@iki.fi \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.chick@citrix.com \
    --cc=xen-devel@lists.xen.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).