All of lore.kernel.org
 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>
Subject: Re: [PATCH net v3 2/3] xen-netback: don't stop dealloc kthread too early
Date: Mon, 11 Aug 2014 15:55:08 +0100	[thread overview]
Message-ID: <53E8D94C.7050905@citrix.com> (raw)
In-Reply-To: <1407751884-9005-3-git-send-email-wei.liu2@citrix.com>

On 11/08/14 11:11, Wei Liu wrote:
> @@ -1525,10 +1537,13 @@ static int xenvif_handle_frag_list(struct xenvif_queue *queue, struct sk_buff *s
>   	/* remove traces of mapped pages and frag_list */
>   	skb_frag_list_init(skb);
>   	uarg = skb_shinfo(skb)->destructor_arg;
> +	/* See comment on set_skb_zerocopy */
> +	if (uarg->callback == xenvif_zerocopy_callback)
This condition is not necessary: uarg->callback shouldn't be anything 
else but this xenvif_zerocopy_callback at this point, unless something 
terribly went wrong. In that case we are doomed anyway :)

> +		xenvif_inc_inflight_packets(queue);
>   	uarg->callback(uarg, true);
>   	skb_shinfo(skb)->destructor_arg = NULL;
>
> -	skb_shinfo(nskb)->tx_flags |= SKBTX_DEV_ZEROCOPY;
> +	set_skb_zerocopy(queue, nskb);
>   	kfree_skb(nskb);
>
>   	return 0;

  reply	other threads:[~2014-08-11 14:55 UTC|newest]

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

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=53E8D94C.7050905@citrix.com \
    --to=zoltan.kiss@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 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.