From: Paul Durrant <paul.durrant@citrix.com>
To: <netdev@vger.kernel.org>, <xen-devel@lists.xenproject.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: [PATCH net-next 4/7] xen-netback: immediately wake tx queue when guest rx queue has space
Date: Mon, 3 Oct 2016 08:31:09 +0100 [thread overview]
Message-ID: <1475479872-23717-5-git-send-email-paul.durrant@citrix.com> (raw)
In-Reply-To: <1475479872-23717-1-git-send-email-paul.durrant@citrix.com>
From: David Vrabel <david.vrabel@citrix.com>
When an skb is removed from the guest rx queue, immediately wake the
tx queue, instead of after processing them.
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
[re-based]
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
---
Cc: Wei Liu <wei.liu2@citrix.com>
---
drivers/net/xen-netback/rx.c | 24 ++++++++----------------
1 file changed, 8 insertions(+), 16 deletions(-)
diff --git a/drivers/net/xen-netback/rx.c b/drivers/net/xen-netback/rx.c
index b0ce4c6..9548709 100644
--- a/drivers/net/xen-netback/rx.c
+++ b/drivers/net/xen-netback/rx.c
@@ -92,27 +92,21 @@ static struct sk_buff *xenvif_rx_dequeue(struct xenvif_queue *queue)
spin_lock_irq(&queue->rx_queue.lock);
skb = __skb_dequeue(&queue->rx_queue);
- if (skb)
+ if (skb) {
queue->rx_queue_len -= skb->len;
+ if (queue->rx_queue_len < queue->rx_queue_max) {
+ struct netdev_queue *txq;
+
+ txq = netdev_get_tx_queue(queue->vif->dev, queue->id);
+ netif_tx_wake_queue(txq);
+ }
+ }
spin_unlock_irq(&queue->rx_queue.lock);
return skb;
}
-static void xenvif_rx_queue_maybe_wake(struct xenvif_queue *queue)
-{
- spin_lock_irq(&queue->rx_queue.lock);
-
- if (queue->rx_queue_len < queue->rx_queue_max) {
- struct net_device *dev = queue->vif->dev;
-
- netif_tx_wake_queue(netdev_get_tx_queue(dev, queue->id));
- }
-
- spin_unlock_irq(&queue->rx_queue.lock);
-}
-
static void xenvif_rx_queue_purge(struct xenvif_queue *queue)
{
struct sk_buff *skb;
@@ -585,8 +579,6 @@ int xenvif_kthread_guest_rx(void *data)
*/
xenvif_rx_queue_drop_expired(queue);
- xenvif_rx_queue_maybe_wake(queue);
-
cond_resched();
}
--
2.1.4
next prev parent reply other threads:[~2016-10-03 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 7:31 [PATCH net-next 0/7] xen-netback: guest rx side refactor Paul Durrant
2016-10-03 7:31 ` [PATCH net-next 1/7] xen-netback: separate guest side rx code into separate module Paul Durrant
2016-10-03 7:31 ` [PATCH net-next 2/7] xen-netback: retire guest rx side prefix GSO feature Paul Durrant
2016-10-03 7:31 ` [PATCH net-next 3/7] xen-netback: refactor guest rx Paul Durrant
2016-10-03 7:31 ` Paul Durrant [this message]
2016-10-03 7:31 ` [PATCH net-next 5/7] xen-netback: process guest rx packets in batches Paul Durrant
2016-10-03 7:31 ` [PATCH net-next 6/7] xen-netback: batch copies for multiple to-guest rx packets Paul Durrant
2016-10-03 7:31 ` [PATCH net-next 7/7] xen/netback: add fraglist support for to-guest rx Paul Durrant
2016-10-04 4:51 ` [PATCH net-next 0/7] xen-netback: guest rx side refactor David Miller
2016-10-04 8:26 ` Paul Durrant
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=1475479872-23717-5-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=david.vrabel@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).