All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Liu <bob.liu@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: justing@spectralogic.com, roger.pau@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: blkif.h: document linux xen-block multi-page ring implementation
Date: Fri, 15 May 2015 18:39:21 +0800	[thread overview]
Message-ID: <5555CCD9.5040305@oracle.com> (raw)
In-Reply-To: <5555C1A9.3060106@citrix.com>


On 05/15/2015 05:51 PM, David Vrabel wrote:
> On 12/05/15 11:58, Bob Liu wrote:
>> After commit 1b1586eeeb8c ("xenbus_client: Extend interface to
>> support multi-page ring"), Linux xenbus driver can support multi-page ring.
>>
>> Based on this interface, we got some impressive improvements by using multi-page
>> ring in xen-block driver. If using 64 pages as the ring, the IOPS increased
>> about 15 times for the throughput testing.
>>
>> The Linux implementation reuses two 'DEPRECATED' nodes('max-ring-pages' and
>> 'num-ring-pages), so that nothing would be broken.
>> Also removed the power of 2 limit and updated the default/max value accordingly.
> 
> You can't drop the power of 2 restriction as there may be frontends that
> support this old option (from before it was deprecated) and these may
> not support non-powers of 2.
> 

After take a closer look I think we can fully reuse the current protocol which
only uses 'ring-page-order' and 'max-ring-page-order'.
And leave 'max-ring-pages' and 'num-ring-pages' to DEPRECATED.

In conclusion, the blkif.h don't need to be modified and I'll update Linux
implementation to use 'ring-page-order' and 'max-ring-page-order' too.
What do you think? Thank you!

Regards,
-Bob

  reply	other threads:[~2015-05-15 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 10:58 [PATCH] xen: blkif.h: document linux xen-block multi-page ring implementation Bob Liu
2015-05-15  9:26 ` Roger Pau Monné
2015-05-15  9:51 ` David Vrabel
2015-05-15 10:39   ` Bob Liu [this message]
2015-05-15 10:45     ` David Vrabel
2015-05-15 15:22 ` Konrad Rzeszutek Wilk
2015-05-15 15:30   ` Paul Durrant
2015-05-15 15:38   ` Jan Beulich
2015-05-15 15:54     ` Konrad Rzeszutek Wilk
2015-05-15 16:02       ` Paul Durrant

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=5555CCD9.5040305@oracle.com \
    --to=bob.liu@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=justing@spectralogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.