From: Andres Lagar-Cavilla <andres.lagarcavilla@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Andres Lagar-Cavilla <andreslc@gridcentric.ca>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org, David Vrabel <david.vrabel@citrix.com>,
Andres Lagar-Cavilla <andres@lagarcavilla.org>
Subject: Re: [PATCH] Xen backend support for paged out grant targets.
Date: Wed, 5 Sep 2012 13:21:56 -0400 [thread overview]
Message-ID: <4FAD394B-6A6C-44F1-AF1C-DC2F935639EE@gmail.com> (raw)
In-Reply-To: <20120905162731.GD11949@phenom.dumpdata.com>
On Sep 5, 2012, at 12:27 PM, Konrad Rzeszutek Wilk wrote:
> On Fri, Aug 31, 2012 at 05:10:56PM +0100, David Vrabel wrote:
>> On 31/08/12 16:42, Andres Lagar-Cavilla wrote:
>>> Actually acted upon your feedback ipso facto:
>>>
>>> commit d5fab912caa1f0cf6be0a6773f502d3417a207b6
>>> Author: Andres Lagar-Cavilla <andres@lagarcavilla.org>
>>> Date: Sun Aug 26 09:45:57 2012 -0400
>>>
>>> Xen backend support for paged out grant targets.
>>
>> This looks mostly fine expect for the #define instead of inline functions.
>>
>>> +#define gnttab_map_grant_no_eagain(_gop) \
>>
>> This name tripped me up previously. As I read this as:
>>
>> gnttab_map_grant_no_[retries_for]_eagain().
>>
>> Perhaps gnttab_map_grant_with_retries() ? Or similar?
>
> gnttab_map_grant_retry ?
>
> Besides that, it looks good to me. Ian Campbell needs to Ack so that
> David Miller (the network maintainer) can pick it up. Please CC them
> both and also LKML.
Sure will do. However, I need to bring attention to the following hunk:
diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
index 682633b..5610fd8 100644
--- a/drivers/net/xen-netback/netback.c
+++ b/drivers/net/xen-netback/netback.c
@@ -635,9 +635,7 @@ static void xen_netbk_rx_action(struct xen_netbk *netbk)
return;
BUG_ON(npo.copy_prod > ARRAY_SIZE(netbk->grant_copy_op));
- ret = HYPERVISOR_grant_table_op(GNTTABOP_copy, &netbk->grant_copy_op,
- npo.copy_prod);
- BUG_ON(ret != 0);
+ gnttab_batch_copy_no_eagain(netbk->grant_copy_op, npo.copy_prod);
It seems like the (extant) code passes a struct gnttab_copy ** to the grant table hypercall (&netbk->grant_copy_op, defined as struct gnttab_copy [])
I "fixed" it to pass a struct gnttab_copy * (netbk->grant_copy_op, no '&'). This matches the other invocation of the grant copy hyper call (in netbk_tx_action). Did I fix it, though? I am confused as to how this could have ever worked.
(cc'ing Ian Campbell for more insight)
Andres
>>
>> David
next prev parent reply other threads:[~2012-09-05 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 16:51 [PATCH] Xen backend support for paged out grant targets andres
2012-08-31 14:32 ` David Vrabel
2012-08-31 14:45 ` Andres Lagar-Cavilla
2012-08-31 15:42 ` Andres Lagar-Cavilla
2012-08-31 16:10 ` David Vrabel
2012-09-05 16:27 ` Konrad Rzeszutek Wilk
2012-09-05 17:21 ` Andres Lagar-Cavilla [this message]
2012-09-12 13:20 ` Andres Lagar-Cavilla
2012-09-12 18:30 ` Konrad Rzeszutek Wilk
2012-08-31 16:54 ` Konrad Rzeszutek Wilk
2012-08-31 19:33 ` Andres Lagar-Cavilla
2012-08-31 21:14 ` Konrad Rzeszutek Wilk
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=4FAD394B-6A6C-44F1-AF1C-DC2F935639EE@gmail.com \
--to=andres.lagarcavilla@gmail.com \
--cc=andres@lagarcavilla.org \
--cc=andreslc@gridcentric.ca \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.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;
as well as URLs for NNTP newsgroup(s).