netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zoltan Kiss <zoltan.kiss@linaro.org>
To: David Vrabel <david.vrabel@citrix.com>, netdev@vger.kernel.org
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [Xen-devel] [PATCHv1 net] xen-netback: notify immediately after pushing Tx response.
Date: Wed, 11 Mar 2015 17:09:04 +0000	[thread overview]
Message-ID: <550076B0.3090404@linaro.org> (raw)
In-Reply-To: <1426087679-13927-1-git-send-email-david.vrabel@citrix.com>



On 11/03/15 15:27, David Vrabel wrote:
> This fixes a performance regression introduced by
> 7fbb9d8415d4a51cf542e87cf3a717a9f7e6aedc (xen-netback: release pending
> index before pushing Tx responses)
>
> Moving the notify outside of the spin locks means it can be delayed a
> long time (if the dealloc thread is descheduled or there is an
> interrupt or softirq).
>
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Reviewed-by: Zoltan Kiss <zoltan.kiss@linaro.org>
> ---
>   drivers/net/xen-netback/netback.c |   23 ++++++++++++-----------
>   1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
> index c4d68d7..7f8a466 100644
> --- a/drivers/net/xen-netback/netback.c
> +++ b/drivers/net/xen-netback/netback.c
> @@ -96,6 +96,7 @@ static void xenvif_idx_release(struct xenvif_queue *queue, u16 pending_idx,
>   static void make_tx_response(struct xenvif_queue *queue,
>   			     struct xen_netif_tx_request *txp,
>   			     s8       st);
> +static void push_tx_responses(struct xenvif_queue *queue);
>
>   static inline int tx_work_todo(struct xenvif_queue *queue);
>
> @@ -655,15 +656,10 @@ static void xenvif_tx_err(struct xenvif_queue *queue,
>   	unsigned long flags;
>
>   	do {
> -		int notify;
> -
>   		spin_lock_irqsave(&queue->response_lock, flags);
>   		make_tx_response(queue, txp, XEN_NETIF_RSP_ERROR);
> -		RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&queue->tx, notify);
> +		push_tx_responses(queue);
>   		spin_unlock_irqrestore(&queue->response_lock, flags);
> -		if (notify)
> -			notify_remote_via_irq(queue->tx_irq);
> -
>   		if (cons == end)
>   			break;
>   		txp = RING_GET_REQUEST(&queue->tx, cons++);
> @@ -1655,7 +1651,6 @@ static void xenvif_idx_release(struct xenvif_queue *queue, u16 pending_idx,
>   {
>   	struct pending_tx_info *pending_tx_info;
>   	pending_ring_idx_t index;
> -	int notify;
>   	unsigned long flags;
>
>   	pending_tx_info = &queue->pending_tx_info[pending_idx];
> @@ -1671,12 +1666,9 @@ static void xenvif_idx_release(struct xenvif_queue *queue, u16 pending_idx,
>   	index = pending_index(queue->pending_prod++);
>   	queue->pending_ring[index] = pending_idx;
>
> -	RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&queue->tx, notify);
> +	push_tx_responses(queue);
>
>   	spin_unlock_irqrestore(&queue->response_lock, flags);
> -
> -	if (notify)
> -		notify_remote_via_irq(queue->tx_irq);
>   }
>
>
> @@ -1697,6 +1689,15 @@ static void make_tx_response(struct xenvif_queue *queue,
>   	queue->tx.rsp_prod_pvt = ++i;
>   }
>
> +static void push_tx_responses(struct xenvif_queue *queue)
> +{
> +	int notify;
> +
> +	RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&queue->tx, notify);
> +	if (notify)
> +		notify_remote_via_irq(queue->tx_irq);
> +}
> +
>   static struct xen_netif_rx_response *make_rx_response(struct xenvif_queue *queue,
>   					     u16      id,
>   					     s8       st,
>

  reply	other threads:[~2015-03-11 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 15:27 [PATCHv1 net] xen-netback: notify immediately after pushing Tx response David Vrabel
2015-03-11 17:09 ` Zoltan Kiss [this message]
2015-03-11 17:44 ` Wei Liu
2015-03-12  3:31 ` 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=550076B0.3090404@linaro.org \
    --to=zoltan.kiss@linaro.org \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).