All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Bob Liu <bob.liu@oracle.com>
Cc: <xen-devel@lists.xen.org>, <david.vrabel@citrix.com>,
	<justing@spectralogic.com>, <konrad.wilk@oracle.com>,
	<paul.durrant@citrix.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] xen/block: add multi-page ring support
Date: Thu, 21 May 2015 15:33:08 +0200	[thread overview]
Message-ID: <555DDE94.3030005@citrix.com> (raw)
In-Reply-To: <555DD790.3040302@oracle.com>

El 21/05/15 a les 15.03, Bob Liu ha escrit:
> On 05/21/2015 07:22 PM, Roger Pau Monné wrote:
>> El 20/05/15 a les 15.10, Bob Liu ha escrit:
>>> +			err = xenbus_scanf(XBT_NIL, dev->otherend,
>>> +					   ring_ref_name, "%u", &ring_ref[i]);
>>
>> No need to split lines unless they are > 100 chars (here and elsewhere).
>>
> 
> Not 82 chars?

Sorry, I must be utterly confused, line length should be 80. Forge about
that comment.

>>> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
>>> index 88e23fd..3d1c6fb 100644
>>> --- a/drivers/block/xen-blkfront.c
>>> +++ b/drivers/block/xen-blkfront.c
>>> @@ -98,7 +98,17 @@ static unsigned int xen_blkif_max_segments = 32;
>>>  module_param_named(max, xen_blkif_max_segments, int, S_IRUGO);
>>>  MODULE_PARM_DESC(max, "Maximum amount of segments in indirect requests (default is 32)");
>>>  
>>> -#define BLK_RING_SIZE __CONST_RING_SIZE(blkif, PAGE_SIZE)
>>> +static unsigned int xen_blkif_max_ring_order;
>>> +module_param_named(max_ring_page_order, xen_blkif_max_ring_order, int, S_IRUGO);
>>> +MODULE_PARM_DESC(max_ring_page_order, "Maximum order of pages to be used as the ring");
>>> +
>>> +#define BLK_RING_SIZE __CONST_RING_SIZE(blkif, PAGE_SIZE * info->nr_ring_pages)
>>
>> Didn't we agreed that this macro should take a explicit info parameter?
>>
> 
> Do you mean define like this?
> #define BLK_RING_SIZE(info) __CONST_RING_SIZE(blkif, PAGE_SIZE * info->nr_ring_pages)

Yes, something like that, but please add parentheses around info, so it
looks like (info)->nr_ring_pages.

Thanks, Roger.

  reply	other threads:[~2015-05-21 13:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 13:10 [PATCH v2 1/2] driver: xen-blkfront: move talk_to_blkback to a more suitable place Bob Liu
2015-05-20 13:10 ` [PATCH v4 2/2] xen/block: add multi-page ring support Bob Liu
2015-05-20 13:21   ` [Xen-devel] " Julien Grall
2015-05-20 14:56     ` Roger Pau Monné
2015-05-20 15:00       ` Julien Grall
2015-05-20 15:00       ` [Xen-devel] " Julien Grall
2015-05-20 23:47         ` Bob Liu
2015-05-20 23:47         ` [Xen-devel] " Bob Liu
2015-05-20 14:56     ` Roger Pau Monné
2015-05-20 13:21   ` Julien Grall
2015-05-21 11:22   ` Roger Pau Monné
2015-05-21 13:03     ` Bob Liu
2015-05-21 13:33       ` Roger Pau Monné [this message]
2015-05-21 13:33       ` Roger Pau Monné
2015-05-21 13:03     ` Bob Liu
2015-05-21 11:22   ` Roger Pau Monné
2015-05-20 13:10 ` Bob Liu
2015-05-21 10:52 ` [PATCH v2 1/2] driver: xen-blkfront: move talk_to_blkback to a more suitable place Roger Pau Monné
2015-05-21 10:52 ` Roger Pau Monné

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=555DDE94.3030005@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=bob.liu@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=justing@spectralogic.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.durrant@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.