From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Paul Durrant <Paul.Durrant@citrix.com>,
Bob Liu <bob.liu@oracle.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
David Vrabel <david.vrabel@citrix.com>,
"justing@spectralogic.com" <justing@spectralogic.com>,
Julien Grall <julien.grall@citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marcus Granado <marcus.granado@citrix.com>,
Rafal Mielniczuk <Rafal.Mielniczuk@citrix.com>
Subject: Re: [PATCH 3/3] xen/block: add multi-page ring support
Date: Tue, 9 Jun 2015 10:21:27 -0400 [thread overview]
Message-ID: <20150609142126.GJ15200@x230> (raw)
In-Reply-To: <5576F325.5050304@citrix.com>
On Tue, Jun 09, 2015 at 04:07:33PM +0200, Roger Pau Monné wrote:
> El 09/06/15 a les 15.39, Konrad Rzeszutek Wilk ha escrit:
> > On Tue, Jun 09, 2015 at 08:52:53AM +0000, Paul Durrant wrote:
> >>> -----Original Message-----
> >>> From: Bob Liu [mailto:bob.liu@oracle.com]
> >>> Sent: 09 June 2015 09:50
> >>> To: Bob Liu
> >>> Cc: xen-devel@lists.xen.org; David Vrabel; justing@spectralogic.com;
> >>> konrad.wilk@oracle.com; Roger Pau Monne; Paul Durrant; Julien Grall; linux-
> >>> kernel@vger.kernel.org
> >>> Subject: Re: [PATCH 3/3] xen/block: add multi-page ring support
> >>>
> >>>
> >>> On 06/03/2015 01:40 PM, Bob Liu wrote:
> >>>> Extend xen/block to support multi-page ring, so that more requests can be
> >>>> issued by using more than one pages as the request ring between blkfront
> >>>> and backend.
> >>>> As a result, the performance can get improved significantly.
> >>>>
> >>>> We got some impressive improvements on our highend iscsi storage cluster
> >>>> backend. If using 64 pages as the ring, the IOPS increased about 15 times
> >>>> for the throughput testing and above doubled for the latency testing.
> >>>>
> >>>> The reason was the limit on outstanding requests is 32 if use only one-page
> >>>> ring, but in our case the iscsi lun was spread across about 100 physical
> >>>> drives, 32 was really not enough to keep them busy.
> >>>>
> >>>> Changes in v2:
> >>>> - Rebased to 4.0-rc6.
> >>>> - Document on how multi-page ring feature working to linux io/blkif.h.
> >>>>
> >>>> Changes in v3:
> >>>> - Remove changes to linux io/blkif.h and follow the protocol defined
> >>>> in io/blkif.h of XEN tree.
> >>>> - Rebased to 4.1-rc3
> >>>>
> >>>> Changes in v4:
> >>>> - Turn to use 'ring-page-order' and 'max-ring-page-order'.
> >>>> - A few comments from Roger.
> >>>>
> >>>> Changes in v5:
> >>>> - Clarify with 4k granularity to comment
> >>>> - Address more comments from Roger
> >>>>
> >>>> Signed-off-by: Bob Liu <bob.liu@oracle.com>
> >>>
> >>> Also tested the windows PV driver which also works fine when multi-page
> >>> ring feature
> >>> was enabled in Linux backend.
> >>> http://www.xenproject.org/downloads/windows-pv-drivers.html
> >>>
> >>
> >> Great! Thanks for verifying that :-)
> >
> > Woot! Bob, could you repost the blkif.h patch for the Xen tree
> > pleas e and also mention the testing part in it please? I think this
> > was the only big 'what if?!' question holding this up.
> >
> >
> > Roger, I put them (patches) on devel/for-jens-4.2 on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> >
> > I think these two patches:
> > drivers: xen-blkback: delay pending_req allocation to connect_ring
> > xen/block: add multi-page ring support
> >
> > are the only ones that haven't been Acked by you (or maybe they
> > have and I missed the Ack?)
>
> Hello,
>
> I was waiting to Ack those because the XenServer storage performance
> folks found out that these patches cause a performance regression on
> some of their tests. I'm adding them to the conversation so they can
This is with multi-page enabled or with the patches but multi-page
disabled (baseline)?
> provide more details about the issues they found, and whether we should
> hold pushing this patches or not.
Or surely fix whatever is causing this.
>
> Roger.
>
next prev parent reply other threads:[~2015-06-09 14:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 5:40 [PATCH 1/3] drivers: xen-blkback: delay pending_req allocation to connect_ring Bob Liu
2015-06-03 5:40 ` [PATCH 2/3] driver: xen-blkfront: move talk_to_blkback to a more suitable place Bob Liu
2015-06-03 5:40 ` [PATCH 3/3] xen/block: add multi-page ring support Bob Liu
2015-06-09 8:50 ` Bob Liu
2015-06-09 8:52 ` Paul Durrant
2015-06-09 13:39 ` Konrad Rzeszutek Wilk
2015-06-09 13:48 ` Bob Liu
2015-06-09 14:07 ` Roger Pau Monné
2015-06-09 14:21 ` Konrad Rzeszutek Wilk [this message]
2015-06-19 20:12 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-06-22 1:20 ` Bob Liu
2015-06-22 13:47 ` Konrad Rzeszutek Wilk
2015-06-22 13:56 ` [PATCH] drivers: xen-blkfront: only talk_to_blkback() when in XenbusStateInitialising Konrad Rzeszutek Wilk
2015-06-22 14:06 ` Konrad Rzeszutek Wilk
2015-06-23 6:23 ` [Xen-devel] " Jan Beulich
2015-06-23 11:57 ` Konrad Rzeszutek Wilk
2015-06-23 12:51 ` [PATCH 3/3] xen/block: add multi-page ring support Marcus Granado
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=20150609142126.GJ15200@x230 \
--to=konrad.wilk@oracle.com \
--cc=Paul.Durrant@citrix.com \
--cc=Rafal.Mielniczuk@citrix.com \
--cc=bob.liu@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=julien.grall@citrix.com \
--cc=justing@spectralogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.granado@citrix.com \
--cc=roger.pau@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