From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: mst@redhat.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org, davem@davemloft.net,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 3/3] virtio-net: clean tx descriptors from rx napi
Date: Sun, 2 Apr 2017 16:10:12 -0400 [thread overview]
Message-ID: <20170402201012.76473-4-willemdebruijn.kernel@gmail.com> (raw)
In-Reply-To: <20170402201012.76473-1-willemdebruijn.kernel@gmail.com>
From: Willem de Bruijn <willemb@google.com>
Amortize the cost of virtual interrupts by doing both rx and tx work
on reception of a receive interrupt if tx napi is enabled. With
VIRTIO_F_EVENT_IDX, this suppresses most explicit tx completion
interrupts for bidirectional workloads.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/net/virtio_net.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
index 95d938e82080..af830eb212bf 100644
--- a/drivers/net/virtio_net.c
+++ b/drivers/net/virtio_net.c
@@ -1030,12 +1030,34 @@ static int virtnet_receive(struct receive_queue *rq, int budget)
return received;
}
+static void free_old_xmit_skbs(struct send_queue *sq);
+
+static void virtnet_poll_cleantx(struct receive_queue *rq)
+{
+ struct virtnet_info *vi = rq->vq->vdev->priv;
+ unsigned int index = vq2rxq(rq->vq);
+ struct send_queue *sq = &vi->sq[index];
+ struct netdev_queue *txq = netdev_get_tx_queue(vi->dev, index);
+
+ if (!sq->napi.weight)
+ return;
+
+ __netif_tx_lock(txq, smp_processor_id());
+ free_old_xmit_skbs(sq);
+ __netif_tx_unlock(txq);
+
+ if (sq->vq->num_free >= 2 + MAX_SKB_FRAGS)
+ netif_wake_subqueue(vi->dev, vq2txq(sq->vq));
+}
+
static int virtnet_poll(struct napi_struct *napi, int budget)
{
struct receive_queue *rq =
container_of(napi, struct receive_queue, napi);
unsigned int received;
+ virtnet_poll_cleantx(rq);
+
received = virtnet_receive(rq, budget);
/* Out of packets? */
--
2.12.2.564.g063fe858b8-goog
next prev parent reply other threads:[~2017-04-02 20:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 20:10 [PATCH net-next 0/3] virtio-net tx napi Willem de Bruijn
2017-04-02 20:10 ` [PATCH net-next 1/3] virtio-net: napi helper functions Willem de Bruijn
2017-04-02 20:10 ` Willem de Bruijn
2017-04-02 20:10 ` [PATCH net-next 2/3] virtio-net: transmit napi Willem de Bruijn
2017-04-02 20:10 ` Willem de Bruijn
2017-04-03 2:30 ` Michael S. Tsirkin
2017-04-03 5:07 ` Willem de Bruijn
2017-04-03 5:07 ` Willem de Bruijn
2017-04-02 20:10 ` Willem de Bruijn [this message]
2017-04-03 2:47 ` [PATCH net-next 3/3] virtio-net: clean tx descriptors from rx napi Michael S. Tsirkin
2017-04-03 5:02 ` Willem de Bruijn
2017-04-07 19:28 ` Michael S. Tsirkin
2017-04-07 20:59 ` Willem de Bruijn
2017-04-07 20:59 ` Willem de Bruijn
2017-04-07 21:10 ` Michael S. Tsirkin
2017-04-07 21:10 ` Michael S. Tsirkin
2017-04-07 21:14 ` Willem de Bruijn
2017-04-07 21:14 ` Willem de Bruijn
2017-04-07 19:28 ` Michael S. Tsirkin
2017-04-03 5:02 ` Willem de Bruijn
2017-04-03 2:47 ` Michael S. Tsirkin
2017-04-02 20:10 ` Willem de Bruijn
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=20170402201012.76473-4-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemb@google.com \
/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.