netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, <xen-devel@lists.xen.org>,
	<netdev@vger.kernel.org>
Cc: <ian.campbell@citrix.com>, <david.vrabel@citrix.com>
Subject: Re: [PATCH net v4 0/3] xen-netback: synchronisation between core driver and netback
Date: Tue, 12 Aug 2014 17:53:46 +0100	[thread overview]
Message-ID: <53EA469A.5030008@citrix.com> (raw)
In-Reply-To: <1407840488-20026-1-git-send-email-wei.liu2@citrix.com>

On 12/08/14 11:48, Wei Liu wrote:
> The zero-copy netback has far more interactions with core network driver than
> the old copying backend. One significant thing is that netback now relies on
> a callback from core driver to correctly release resources.
>
> However correct synchronisation between core driver and netback is missing.
> Currently netback relies on a loop to wait for core driver to release
> resources. This is proven not enough and erroneous recently, partly due to code
> structure, partly due to missing synchronisation. Short-live domains like
> OpenMirage unikernels can easily trigger race in backend, rendering backend
> unresponsive.
>
> This patch series aims to slove this issue by introducing proper
> synchronisation between core driver and netback.
>
> Wei.
>
> Chagges in v4:
> * avoid using wait queue
> * remove dedicated loop for netif_napi_del
> * remove unnecessary check on callback
>
> Change in v3: improve commit message in patch 1
>
> Change in v2: fix Zoltan's email address in commit message
>
>
> Wei Liu (3):
>    xen-netback: move NAPI add/remove calls
>    xen-netback: don't stop dealloc kthread too early
>    xen-netback: remove loop waiting function
>
>   drivers/net/xen-netback/common.h    |    5 ++++
>   drivers/net/xen-netback/interface.c |   56 ++++++++++++++---------------------
>   drivers/net/xen-netback/netback.c   |   26 +++++++++++-----
>   3 files changed, 47 insertions(+), 40 deletions(-)
>

Looks good for me.

Acked-by: Zoltan Kiss <zoltan.kiss@citrix.com>

  parent reply	other threads:[~2014-08-12 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 10:48 [PATCH net v4 0/3] xen-netback: synchronisation between core driver and netback Wei Liu
2014-08-12 10:48 ` [PATCH net v4 1/3] xen-netback: move NAPI add/remove calls Wei Liu
2014-08-12 10:48 ` [PATCH net v4 2/3] xen-netback: don't stop dealloc kthread too early Wei Liu
2014-08-12 10:48 ` [PATCH net v4 3/3] xen-netback: remove loop waiting function Wei Liu
2014-08-12 16:53 ` Zoltan Kiss [this message]
2014-08-12 21:42 ` [PATCH net v4 0/3] xen-netback: synchronisation between core driver and netback David Miller

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=53EA469A.5030008@citrix.com \
    --to=zoltan.kiss@citrix.com \
    --cc=david.vrabel@citrix.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 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).