From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Oliver Chick (Intern)" <oliver.chick@citrix.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] [PATCH v2] Persistent grant maps for xen blk drivers
Date: Tue, 9 Oct 2012 18:39:18 +0200 [thread overview]
Message-ID: <50745336.5080101@citrix.com> (raw)
In-Reply-To: <506061E6020000780009D4AB@nat28.tlf.novell.com>
On 24/09/12 13:36, Jan Beulich wrote:
>>>> On 21.09.12 at 17:52, Oliver Chick <oliver.chick@citrix.com> wrote:
>> Changes since v1:
>>
>> * Maximum number of persistent grants per device now 64, rather than
>> 256, as this is the actual maxmimum request in a (1 page) ring.
>
> As said previously, I don't see why this needs to have a separate
> #define at all - it's simply __RING_SIZE(). No adding this would
> also imply that - apart from perhaps documenting the new xenstore
> nodes - io/blkif.h would need changing at all (which otherwise would
> require a hypervisor side patch to be submitted too).
I've been working on this a little bit more, and __RING_SIZE returns 32
for all ring types (blkif, blkif_x86_32 and blkif_x86_64), any specific
reason to choose __RING_SIZE()*2?
prev parent reply other threads:[~2012-10-09 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 15:52 [PATCH v2] Persistent grant maps for xen blk drivers Oliver Chick
2012-09-21 18:41 ` Konrad Rzeszutek Wilk
2012-09-21 18:56 ` Konrad Rzeszutek Wilk
2012-09-21 20:46 ` Konrad Rzeszutek Wilk
2012-09-24 14:38 ` Andres Lagar-Cavilla
2012-09-24 15:06 ` Konrad Rzeszutek Wilk
2012-09-24 15:21 ` Andres Lagar-Cavilla
2012-09-27 15:49 ` Oliver Chick
2012-09-24 11:36 ` [Xen-devel] " Jan Beulich
2012-09-24 11:44 ` Ian Campbell
2012-10-09 16:39 ` Roger Pau Monné [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=50745336.5080101@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--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 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.