From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: pradeepv@amazon.com,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Add multi-page shared ring support to xen-blkfront/back
Date: Wed, 3 Aug 2011 14:17:32 -0400 [thread overview]
Message-ID: <20110803181732.GA32430@dumpdata.com> (raw)
In-Reply-To: <4B4CB6AE.70005@citrix.com>
On Tue, Jan 12, 2010 at 05:51:42PM +0000, Paul Durrant wrote:
> Paul Durrant wrote:
> >These patches add support for multi-page shared rings to xen-blkfront/back.
> >Shared rings must always be a power of 2 in size and so the size is controlled
> >by the new 'max_ring_page_order' module parameter of xen-blkback. This defaults
> >to 0 so operationally there should be no difference with these patches in place.
> >The maximum value of 'max_ring_page_order' is currently limited to 2
> >(i.e. 4 pages).
> >xen-blkfront will always use the largest shared ring size supported by the back
> >end. To override this and continue to use a single page ring, as before, set the
> >'allow_multi_page_ring' module parameter to 0.
Hey Paul,
Would it be possible to rebase this on 3.0? How is it different from the
one posted some time ago by .. um, somebody else?
prev parent reply other threads:[~2011-08-03 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 17:44 Add multi-page shared ring support to xen-blkfront/back Paul Durrant
2010-01-12 17:44 ` [PATCH 1/2] Add multi-page ring support to xen-blkback Paul Durrant
2010-01-12 17:44 ` [PATCH 2/2] Add multi-page ring support to xen-blkfront Paul Durrant
2010-01-12 17:51 ` Add multi-page shared ring support to xen-blkfront/back Paul Durrant
2010-01-12 20:58 ` Add multi-page shared ring support toxen-blkfront/back James Harper
2010-01-12 21:22 ` Daniel Stodden
2010-01-13 6:03 ` James Harper
2010-01-12 23:52 ` Add multi-page shared ring support to xen-blkfront/back Dan Magenheimer
2011-08-03 18:17 ` Konrad Rzeszutek Wilk [this message]
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=20110803181732.GA32430@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=paul.durrant@citrix.com \
--cc=pradeepv@amazon.com \
--cc=xen-devel@lists.xensource.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).