From: Andrew Bennieston <andrew.bennieston@citrix.com>
To: annie li <annie.li@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>, <netdev@vger.kernel.org>,
<ian.campbell@citrix.com>, <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] [PATCH net-next] xen-netfront: clean up code in xennet_release_rx_bufs
Date: Wed, 15 Jan 2014 15:35:00 +0000 [thread overview]
Message-ID: <52D6AAA4.7090108@citrix.com> (raw)
In-Reply-To: <52D697FB.3000304@oracle.com>
On 15/01/14 14:15, annie li wrote:
>
> On 2014-1-15 19:02, Andrew Bennieston wrote:
>> On 15/01/14 10:07, Wei Liu wrote:
>>> On Fri, Jan 10, 2014 at 06:48:38AM +0800, Annie Li wrote:
>>>> Current netfront only grants pages for grant copy, not for grant
>>>> transfer, so
>>>> remove corresponding transfer code and add receiving copy code in
>>>> xennet_release_rx_bufs.
>>>>
>>>
>>> This path seldom gets call -- not that many people unload xen-netfront
>>> driver. If Annie has tested this patch and it works as expected I think
>>> it's fine.
>>>
>> In XenServer we have seen a number of cases where unplugging and
>> replugging VIFs results in leakage of grant references, eventually
>> leading to a case where you cannot plug a VIF (after ~ 400 such
>> cycles)...
>>
>> It's worth pointing out, as far as this patch is concerned, that
>> gnttab_end_foreign_access() can fail,
>
> Just like what Wei mentioned, it is gnttab_end_foreign_access_ref here,
> right?
Yes, sorry - I forgot to type the _ref part!
>
>> which is not taken into account here.
>
> Good point, gnttab_end_foreign_access_ref fails for grant which is in use.
>
> Thanks
> Annie
>>
>> Andrew.
>>
>>> I'm not netfront maintainer but I'm happy to add
>>> Acked-by: Wei Liu <wei.liu2@citrix.com>
>>> if Annie confirms she's tested this patch.
>>>
>>> Wei.
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
>>>
>>
>
next prev parent reply other threads:[~2014-01-15 15:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 22:48 [Xen-devel][PATCH net-next] xen-netfront: clean up code in xennet_release_rx_bufs Annie Li
2014-01-14 23:28 ` David Miller
2014-01-16 6:04 ` [PATCH " annie li
2014-01-16 6:04 ` [Xen-devel] " annie li
2014-01-14 23:28 ` David Miller
2014-01-15 10:07 ` Wei Liu
2014-01-15 10:07 ` [Xen-devel][PATCH " Wei Liu
2014-01-15 11:02 ` [Xen-devel] [PATCH " Andrew Bennieston
2014-01-15 11:14 ` Wei Liu
2014-01-15 11:14 ` Wei Liu
2014-01-15 14:15 ` [Xen-devel] " annie li
2014-01-15 15:35 ` Andrew Bennieston
2014-01-15 15:35 ` Andrew Bennieston [this message]
2014-01-15 14:15 ` annie li
2014-01-15 11:02 ` Andrew Bennieston
2014-01-15 11:20 ` David Vrabel
2014-01-15 11:20 ` [Xen-devel] " David Vrabel
2014-01-15 11:42 ` Wei Liu
2014-01-15 11:52 ` David Vrabel
2014-01-15 14:17 ` annie li
2014-01-15 14:17 ` [Xen-devel] " annie li
2014-01-15 14:32 ` Wei Liu
2014-01-15 14:32 ` Wei Liu
2014-01-15 15:13 ` David Vrabel
2014-01-15 15:13 ` [Xen-devel] " David Vrabel
2014-01-16 5:59 ` annie li
2014-01-16 5:59 ` annie li
2014-01-15 11:52 ` David Vrabel
2014-01-15 11:42 ` Wei Liu
2014-01-15 14:16 ` annie li
2014-01-15 14:16 ` [Xen-devel] " annie li
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=52D6AAA4.7090108@citrix.com \
--to=andrew.bennieston@citrix.com \
--cc=annie.li@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@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.