[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F1AA0F73-4A5F-4B2A-A948-79E854A52BAE@neclab.eu>
Date: Tue, 19 May 2015 10:19:23 +0000
From: Joao Martins <Joao.Martins@...lab.eu>
To: David Vrabel <david.vrabel@...rix.com>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"wei.liu2@...rix.com" <wei.liu2@...rix.com>,
"ian.campbell@...rix.com" <ian.campbell@...rix.com>,
"boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>
Subject: Re: [Xen-devel] [RFC PATCH 09/13] xen-netfront: move grant_{ref,
page} to struct grant
On 18 May 2015, at 17:44, David Vrabel <david.vrabel@...rix.com> wrote:
> On 12/05/15 18:18, Joao Martins wrote:
>> Refactors a little bit how grants are stored by moving
>> grant_rx_ref/grant_tx_ref and grant_tx_page to its
>> own structure, namely struct grant.
>
> Reviewed-by: David Vrabel <david.vrabel@...rix.com>
>
> Although...
>
>> --- a/drivers/net/xen-netfront.c
>> +++ b/drivers/net/xen-netfront.c
>> @@ -87,6 +87,11 @@ struct netfront_cb {
>> /* IRQ name is queue name with "-tx" or "-rx" appended */
>> #define IRQ_NAME_SIZE (QUEUE_NAME_SIZE + 3)
>>
>> +struct grant {
>> + grant_ref_t ref;
>> + struct page *page;
>> +};
>
> Is this sort of structure (and the following patch) useful for other
> frontends?
Perhaps not. It seems that blkfront is the only one that uses similar structure.
Though it creates a struct grant containing an additional struct list_node
field that is used for the free grants list within blkfront. In my case I
extend the struct grant later on the patch "xen-netfront: implement RX
persistent grants" to have the struct ubuf_info.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists