From: Willem de Bruijn <willemdebruijn.kernel@gmail.com> Date: 2017-03-03 14:45:50
From: Willem de Bruijn <willemb@google.com>
Add napi for virtio-net transmit completion processing. Based on
previous patchsets by Jason Wang:
[RFC V7 PATCH 0/7] enable tx interrupts for virtio-net
http://lkml.iu.edu/hypermail/linux/kernel/1505.3/00245.html
This patchset is not ready for submission yet, but it is time for
another checkpoint. Among others, it requires more testing with
more diverse workloads.
Before commit b0c39dbdc204 ("virtio_net: don't free buffers in xmit
ring") the virtio-net driver would free transmitted packets on
transmission of new packets in ndo_start_xmit and, to catch the edge
case when no new packet is sent, also in a timer at 10HZ.
A timer can cause long stalls. VIRTIO_F_NOTIFY_ON_EMPTY avoids stalls
due to low free descriptor count. It does not address a stalls due to
low socket SO_SNDBUF. Increasing timer frequency decreases that stall
time, but increases interrupt rate and, thus, cycle count.
Currently, with no timer, packets are freed only at ndo_start_xmit.
Latency of consume_skb is now unbounded. To avoid a deadlock if a sock
reaches SO_SNDBUF, packets are orphaned on tx. This breaks TCP small
queues.
Reenable TCP small queues by removing the orphan. Instead of using a
timer, convert the driver to regular tx napi. This does not have the
unresolved stall issue and does not have any frequency to tune.
By keeping interrupts enabled by default, napi increases tx
interrupt rate. VIRTIO_F_EVENT_IDX avoids sending an interrupt if
one is already unacknowledged, so makes this more feasible today.
Combine that with two optimizations that bring interrupt rate
back in line with the existing code:
Interrupt coalescing delays interrupts until a number of events
accrue or a timer fires.
Tx completion cleaning on rx interrupts elides most explicit tx
interrupts by relying on the fact that many rx interrupts fire.
Tested by running {1, 10, 100} TCP_STREAM and TCP_RR tests from a
guest to a server on the host, on an x86_64 Haswell. The guest
runs 4 vCPUs pinned to 4 cores. vhost and the test server are
pinned to a core each.
All results are the median of 5 runs, with variance well < 10%.
Used neper (github.com/google/neper) as test process. Tests used
experimental_zcopy=0. This is likely no longer needed.
Napi increases single stream throughput, but increases cycle cost
across the board. Interrupt moderation ("+vhost") reverts both, if
not fully. For this workload with ACKs in the return path, the
last optimization ("at-rx") is more effective. For UDP this is
likely not true.
upstream napi +vhost +at-rx +v+at-rx
Stream:
1x:
Mbps 30182 38782 30106 38002 32842
Gcycles 405 499 386 403 417
10x:
Mbps 40441 40575 41638 40260 41299
Gcycles 438 545 430 416 416
100x:
Mbps 34049 34697 34763 34637 34259
Gcycles 441 545 433 415 422
Latency (us):
1x:
p50 24 24 24 21 24
p99 27 27 27 26 27
Gcycles 299 430 432 312 297
10x:
p50 30 31 31 42 31
p99 40 46 48 52 42
Gcycles 347 423 471 322 463
100x:
p50 155 151 163 306 161
p99 337 329 352 361 349
Gcycles 340 421 463 306 441
Lower throughput at 100x vs 10x can be (at least in part)
explained by looking at bytes per packet sent (nstat). It likely
also explains the lower throughput of 1x for some variants.
upstream:
N=1 bytes/pkt=16581
N=10 bytes/pkt=61513
N=100 bytes/pkt=51558
at_rx:
N=1 bytes/pkt=65204
N=10 bytes/pkt=65148
N=100 bytes/pkt=56840
For this experiment, vhost has 64 frames and usecs thresholds.
Configuring this from the guest requires additional patches to qemu.
Temporary patch:
@@ -846,9 +845,6 @@ static int vhost_net_open(struct inode *inode, struct file *f)
vhost_poll_init(n->poll + VHOST_NET_VQ_TX, handle_tx_net, POLLOUT, dev);
vhost_poll_init(n->poll + VHOST_NET_VQ_RX, handle_rx_net, POLLIN, dev);
- vqs[VHOST_NET_VQ_TX]->max_coalesce_ktime = ktime_set(0, 64 * NSEC_PER_USEC);
- vqs[VHOST_NET_VQ_TX]->max_coalesce_frames = 64;
-
f->private_data = n;
TODO
- restart timer if trylock failed and lock not held by hande_tx
- start timer only at end of handle_tx and kill at start
- make napi_tx configurable
- increase test coverage
- 4KB TCP_RR
- UDP
- multithreaded sender
- with experimental_zcopytx
Willem de Bruijn (4):
virtio-net: napi helper functions
virtio-net: transmit napi
vhost: interrupt coalescing support
virtio-net: clean tx descriptors from rx napi
drivers/net/virtio_net.c | 157 +++++++++++++++++++++++++++++++++------------
drivers/vhost/vhost.c | 74 ++++++++++++++++++++-
drivers/vhost/vhost.h | 12 ++++
include/uapi/linux/vhost.h | 11 ++++
4 files changed, 211 insertions(+), 43 deletions(-)
--
2.12.0.rc1.440.g5b76565f74-goog
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com> Date: 2017-03-03 14:45:44
From: Willem de Bruijn <willemb@google.com>
Prepare virtio-net for tx napi by converting existing napi code to
use helper functions. This also deduplicates some logic.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/net/virtio_net.c | 65 ++++++++++++++++++++++++++----------------------
1 file changed, 35 insertions(+), 30 deletions(-)
@@ -936,27 +956,20 @@ static void skb_recv_done(struct virtqueue *rvq)structvirtnet_info*vi=rvq->vdev->priv;structreceive_queue*rq=&vi->rq[vq2rxq(rvq)];-/* Schedule NAPI, Suppress further interrupts if successful. */-if(napi_schedule_prep(&rq->napi)){-virtqueue_disable_cb(rvq);-__napi_schedule(&rq->napi);-}+virtqueue_napi_schedule(&rq->napi,rvq);}-staticvoidvirtnet_napi_enable(structreceive_queue*rq)+staticvoidvirtnet_napi_enable(structvirtqueue*vq,structnapi_struct*napi){-napi_enable(&rq->napi);+napi_enable(napi);/* If all buffers were filled by other side before we napi_enabled, we-*won'tgetanotherinterrupt,soprocessanyoutstandingpackets-*now.virtnet_pollwantsre-enablethequeue,sowedisablehere.-*WesynchronizeagainstinterruptsviaNAPI_STATE_SCHED*/-if(napi_schedule_prep(&rq->napi)){-virtqueue_disable_cb(rq->vq);-local_bh_disable();-__napi_schedule(&rq->napi);-local_bh_enable();-}+*won'tgetanotherinterrupt,soprocessanyoutstandingpacketsnow.+*Calllocal_bh_enableaftertotriggersoftIRQprocessing.+*/+local_bh_disable();+virtqueue_napi_schedule(napi,vq);+local_bh_enable();}staticvoidrefill_work(structwork_struct*work)
@@ -971,7 +984,7 @@ static void refill_work(struct work_struct *work)napi_disable(&rq->napi);still_empty=!try_fill_recv(vi,rq,GFP_KERNEL);-virtnet_napi_enable(rq);+virtnet_napi_enable(rq->vq,&rq->napi);/* In theory, this can happen: if we don't get any buffers in*wewill*never*trytofillagain.
@@ -1011,21 +1024,13 @@ static int virtnet_poll(struct napi_struct *napi, int budget){structreceive_queue*rq=container_of(napi,structreceive_queue,napi);-unsignedintr,received;+unsignedintreceived;received=virtnet_receive(rq,budget);/* Out of packets? */-if(received<budget){-r=virtqueue_enable_cb_prepare(rq->vq);-if(napi_complete_done(napi,received)){-if(unlikely(virtqueue_poll(rq->vq,r))&&-napi_schedule_prep(napi)){-virtqueue_disable_cb(rq->vq);-__napi_schedule(napi);-}-}-}+if(received<budget)+virtqueue_napi_complete(napi,rq->vq,received);returnreceived;}
@@ -1040,7 +1045,7 @@ static int virtnet_open(struct net_device *dev)/* Make sure we have some buffers: if oom use wq. */if(!try_fill_recv(vi,&vi->rq[i],GFP_KERNEL))schedule_delayed_work(&vi->refill,0);-virtnet_napi_enable(&vi->rq[i]);+virtnet_napi_enable(vi->rq[i].vq,&vi->rq[i].napi);}return0;
@@ -1737,7 +1742,7 @@ static int virtnet_restore_up(struct virtio_device *vdev)schedule_delayed_work(&vi->refill,0);for(i=0;i<vi->max_queue_pairs;i++)-virtnet_napi_enable(&vi->rq[i]);+virtnet_napi_enable(vi->rq[i].vq,&vi->rq[i].napi);}netif_device_attach(vi->dev);
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com> Date: 2017-03-03 14:47:32
From: Willem de Bruijn <willemb@google.com>
Implement standard interrupt coalescing for vhost based drivers,
delaying interrupts up to a maximum latency or number of events.
Interrupt moderation is customary for network devices, where it
is specified as ethtool -K $DEV rx-frames N rx-usecs M. Add the
same variable to vhost and integrate into vhost_notify. Add a
timer to track the time bound.
The feature is configured from the guest over PCI. Add new control
operations VHOST_SET_VRING_COALESCE and VHOST_GET_VRING_COALESCE to
communicate these features between the hypervisor and vhost.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/vhost/vhost.c | 76 +++++++++++++++++++++++++++++++++++++++++++++-
drivers/vhost/vhost.h | 12 ++++++++
include/uapi/linux/vhost.h | 11 +++++++
3 files changed, 98 insertions(+), 1 deletion(-)
@@ -394,6 +397,22 @@ static void vhost_dev_free_iovecs(struct vhost_dev *dev)vhost_vq_free_iovecs(dev->vqs[i]);}+voidvhost_signal(structvhost_dev*dev,structvhost_virtqueue*vq);+staticenumhrtimer_restartvhost_coalesce_timer(structhrtimer*timer)+{+structvhost_virtqueue*vq=+container_of(timer,structvhost_virtqueue,ctimer);++if(mutex_trylock(&vq->mutex)){+vq->coalesce_frames=vq->max_coalesce_frames;+vhost_signal(vq->dev,vq);+mutex_unlock(&vq->mutex);+}++/* TODO: restart if lock failed and not held by handle_tx */+returnHRTIMER_NORESTART;+}+voidvhost_dev_init(structvhost_dev*dev,structvhost_virtqueue**vqs,intnvqs){
@@ -1279,6 +1301,7 @@ long vhost_vring_ioctl(struct vhost_dev *d, int ioctl, void __user *argp)structvhost_vring_states;structvhost_vring_filef;structvhost_vring_addra;+structvhost_vring_coalescec;u32idx;longr;
@@ -1335,6 +1358,30 @@ long vhost_vring_ioctl(struct vhost_dev *d, int ioctl, void __user *argp)if(copy_to_user(argp,&s,sizeofs))r=-EFAULT;break;+caseVHOST_SET_VRING_COALESCE:+if(copy_from_user(&c,argp,sizeof(c))){+r=-EFAULT;+break;+}++if((c.max_coalesce_frames&&!c.max_coalesce_usecs)||+(c.max_coalesce_usecs&&!c.max_coalesce_frames)||+(c.max_coalesce_usecs>10000)||+(c.max_coalesce_frames>1024)){+r=-EINVAL;+break;+}++vq->max_coalesce_ktime=ns_to_ktime(c.max_coalesce_usecs*+NSEC_PER_USEC);+vq->max_coalesce_frames=c.max_coalesce_frames;+break;+caseVHOST_GET_VRING_COALESCE:+c.max_coalesce_usecs=ktime_to_us(vq->max_coalesce_ktime);+c.max_coalesce_frames=vq->max_coalesce_frames;+if(copy_to_user(argp,&c,sizeof(c)))+r=-EFAULT;+break;caseVHOST_SET_VRING_ADDR:if(copy_from_user(&a,argp,sizeofa)){r=-EFAULT;
@@ -1418,6 +1465,11 @@ long vhost_vring_ioctl(struct vhost_dev *d, int ioctl, void __user *argp)break;}if(eventfp!=vq->call){+/* do not update while timer is active */+if(hrtimer_active(&vq->ctimer)){+hrtimer_cancel(&vq->ctimer);+vhost_signal(vq->dev,vq);+}filep=vq->call;ctx=vq->call_ctx;vq->call=eventfp;
@@ -2112,6 +2164,10 @@ static int __vhost_add_used_n(struct vhost_virtqueue *vq,*signalsatleastoncein2^16andremovethis.*/if(unlikely((u16)(new-vq->signalled_used)<(u16)(new-old)))vq->signalled_used_valid=false;++if(vq->max_coalesce_frames)+vq->coalesce_frames+=count;+return0;}
@@ -2162,6 +2226,14 @@ static bool vhost_notify(struct vhost_dev *dev, struct vhost_virtqueue *vq)unlikely(vq->avail_idx==vq->last_avail_idx))returntrue;+if(vq->coalesce_frames<vq->max_coalesce_frames){+if(!hrtimer_active(&vq->ctimer))+hrtimer_start(&vq->ctimer,vq->max_coalesce_ktime,+HRTIMER_MODE_REL);+returnfalse;+}+vhost_coalesce_reset(vq);+if(!vhost_has_feature(vq,VIRTIO_RING_F_EVENT_IDX)){__virtio16flags;/* Flush out used index updates. This is paired
@@ -2208,8 +2280,10 @@ static bool vhost_notify(struct vhost_dev *dev, struct vhost_virtqueue *vq)voidvhost_signal(structvhost_dev*dev,structvhost_virtqueue*vq){/* Signal the Guest tell them we used something up. */-if(vq->call_ctx&&vhost_notify(dev,vq))+if(vq->call_ctx&&vhost_notify(dev,vq)){eventfd_signal(vq->call_ctx,1);+vhost_coalesce_reset(vq);+}}EXPORT_SYMBOL_GPL(vhost_signal);
@@ -119,6 +119,18 @@ struct vhost_virtqueue {/* Last used index value we have signalled on */boolsignalled_used_valid;+/* Maximum time to wait before genearting an interrupt */+ktime_tmax_coalesce_ktime;++/* Maximum number of pending frames before generating an interrupt */+u32max_coalesce_frames;++/* The number of frames pending an interrupt */+u32coalesce_frames;++/* Timer used to trigger an coalesced interrupt */+structhrtimerctimer;+/* Log writes to used structure. */boollog_used;u64log_addr;
@@ -143,6 +148,12 @@ struct vhost_memory {#define VHOST_SET_VRING_ENDIAN _IOW(VHOST_VIRTIO, 0x13, struct vhost_vring_state)#define VHOST_GET_VRING_ENDIAN _IOW(VHOST_VIRTIO, 0x14, struct vhost_vring_state)+/* Set coalescing parameters for the ring. */+#define VHOST_SET_VRING_COALESCE _IOW(VHOST_VIRTIO, 0x15, \+structvhost_vring_coalesce)+/* Get coalescing parameters for the ring. */+#define VHOST_GET_VRING_COALESCE _IOW(VHOST_VIRTIO, 0x16, \+structvhost_vring_coalesce)/* The following ioctls use eventfd file descriptors to signal and poll*forevents.*/
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com> Date: 2017-03-06 17:32:20
On Mon, Mar 6, 2017 at 4:28 AM, Jason Wang [off-list ref] wrote:
On 2017年03月03日 22:39, Willem de Bruijn wrote:
quoted
+void vhost_signal(struct vhost_dev *dev, struct vhost_virtqueue *vq);
+static enum hrtimer_restart vhost_coalesce_timer(struct hrtimer *timer)
+{
+ struct vhost_virtqueue *vq =
+ container_of(timer, struct vhost_virtqueue, ctimer);
+
+ if (mutex_trylock(&vq->mutex)) {
+ vq->coalesce_frames = vq->max_coalesce_frames;
+ vhost_signal(vq->dev, vq);
+ mutex_unlock(&vq->mutex);
+ }
+
+ /* TODO: restart if lock failed and not held by handle_tx */
+ return HRTIMER_NORESTART;
+}
+
Then we may lose an interrupt forever if no new tx request? I believe we
need e.g vhost_poll_queue() here.
Absolutely, I need to fix this. The common case for failing to grab
the lock is competition with handle_tx. With careful coding we can
probably avoid scheduling another run with vhost_poll_queue in
the common case.
Your patch v7 cancels the pending hrtimer at the start of handle_tx.
I need to reintroduce that, and also only schedule a timer at the end
of handle_tx, not immediately when vq->coalesce_frames becomes
non-zero.
From: Jason Wang <hidden> Date: 2017-03-08 03:25:34
On 2017年03月07日 01:31, Willem de Bruijn wrote:
On Mon, Mar 6, 2017 at 4:28 AM, Jason Wang [off-list ref] wrote:
quoted
On 2017年03月03日 22:39, Willem de Bruijn wrote:
quoted
+void vhost_signal(struct vhost_dev *dev, struct vhost_virtqueue *vq);
+static enum hrtimer_restart vhost_coalesce_timer(struct hrtimer *timer)
+{
+ struct vhost_virtqueue *vq =
+ container_of(timer, struct vhost_virtqueue, ctimer);
+
+ if (mutex_trylock(&vq->mutex)) {
+ vq->coalesce_frames = vq->max_coalesce_frames;
+ vhost_signal(vq->dev, vq);
+ mutex_unlock(&vq->mutex);
+ }
+
+ /* TODO: restart if lock failed and not held by handle_tx */
+ return HRTIMER_NORESTART;
+}
+
Then we may lose an interrupt forever if no new tx request? I believe we
need e.g vhost_poll_queue() here.
Absolutely, I need to fix this. The common case for failing to grab
the lock is competition with handle_tx. With careful coding we can
probably avoid scheduling another run with vhost_poll_queue in
the common case.
Yes, probably add some checking after releasing the mutex_lock in
handle_tx().
Thans
Your patch v7 cancels the pending hrtimer at the start of handle_tx.
I need to reintroduce that, and also only schedule a timer at the end
of handle_tx, not immediately when vq->coalesce_frames becomes
non-zero.
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com> Date: 2017-03-03 14:47:47
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. Together VIRTIO_F_EVENT_IDX and
vhost interrupt moderation, this suppresses most explicit tx
completion interrupts for bidirectional workloads.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/net/virtio_net.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
@@ -1031,6 +1031,23 @@ static int virtnet_receive(struct receive_queue *rq, int budget)returnreceived;}+staticunsignedintfree_old_xmit_skbs(structsend_queue*sq,intbudget);++staticvoidvirtnet_poll_cleantx(structreceive_queue*rq)+{+structvirtnet_info*vi=rq->vq->vdev->priv;+unsignedintindex=vq2rxq(rq->vq);+structsend_queue*sq=&vi->sq[index];+structnetdev_queue*txq=netdev_get_tx_queue(vi->dev,index);++__netif_tx_lock(txq,smp_processor_id());+free_old_xmit_skbs(sq,sq->napi.weight);+__netif_tx_unlock(txq);++if(sq->vq->num_free>=2+MAX_SKB_FRAGS)+netif_wake_subqueue(vi->dev,vq2txq(sq->vq));+}+staticintvirtnet_poll(structnapi_struct*napi,intbudget){structreceive_queue*rq=
@@ -1039,6 +1056,8 @@ static int virtnet_poll(struct napi_struct *napi, int budget)received=virtnet_receive(rq,budget);+virtnet_poll_cleantx(rq);+/* Out of packets? */if(received<budget)virtqueue_napi_complete(napi,rq->vq,received);
From: Jason Wang <hidden> Date: 2017-03-06 09:34:27
On 2017年03月03日 22:39, Willem de Bruijn wrote:
quoted hunk
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. Together VIRTIO_F_EVENT_IDX and
vhost interrupt moderation, this suppresses most explicit tx
completion interrupts for bidirectional workloads.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/net/virtio_net.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
@@ -1031,6 +1031,23 @@ static int virtnet_receive(struct receive_queue *rq, int budget)returnreceived;}+staticunsignedintfree_old_xmit_skbs(structsend_queue*sq,intbudget);++staticvoidvirtnet_poll_cleantx(structreceive_queue*rq)+{+structvirtnet_info*vi=rq->vq->vdev->priv;+unsignedintindex=vq2rxq(rq->vq);+structsend_queue*sq=&vi->sq[index];+structnetdev_queue*txq=netdev_get_tx_queue(vi->dev,index);++__netif_tx_lock(txq,smp_processor_id());+free_old_xmit_skbs(sq,sq->napi.weight);+__netif_tx_unlock(txq);
Should we check tx napi weight here? Or this was treated as an
independent optimization?
quoted hunk
+
+ 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 =
@@ -1039,6 +1056,8 @@ static int virtnet_poll(struct napi_struct *napi, int budget) received = virtnet_receive(rq, budget);+ virtnet_poll_cleantx(rq);+
Better to do the before virtnet_receive() consider refill may allocate
memory for rx buffers.
Btw, if this is proved to be more efficient. In the future we may
consider to:
1) use a single interrupt for both rx and tx
2) use a single napi to handle both rx and tx
Thanks
/* Out of packets? */
if (received < budget)
virtqueue_napi_complete(napi, rq->vq, received);
Should we check tx napi weight here? Or this was treated as an independent
optimization?
Good point. This was not intended to run in no-napi mode as is.
With interrupts disabled most of the time in that mode, I don't
expect it to be worthwhile using in that case. I'll add the check
for sq->napi.weight != 0.
quoted
+
+ 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 =
@@ -1039,6 +1056,8 @@ static int virtnet_poll(struct napi_struct *napi,
int budget)
received = virtnet_receive(rq, budget);
+ virtnet_poll_cleantx(rq);
+
Better to do the before virtnet_receive() consider refill may allocate
memory for rx buffers.
Will do.
Btw, if this is proved to be more efficient. In the future we may consider
to:
1) use a single interrupt for both rx and tx
2) use a single napi to handle both rx and tx
Should we check tx napi weight here? Or this was treated as an independent
optimization?
Good point. This was not intended to run in no-napi mode as is.
With interrupts disabled most of the time in that mode, I don't
expect it to be worthwhile using in that case. I'll add the check
for sq->napi.weight != 0.
I'm wrong here. Rx interrupts are not disabled, of course. It is
probably worth benchmarking, then.
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com> Date: 2017-03-03 15:35:55
From: Willem de Bruijn <willemb@google.com>
Convert virtio-net to a standard napi tx completion path. This enables
better TCP pacing using TCP small queues and increases single stream
throughput.
The virtio-net driver currently cleans tx descriptors on transmission
of new packets in ndo_start_xmit. Latency depends on new traffic, so
is unbounded. To avoid deadlock when a socket reaches its snd limit,
packets are orphaned on tranmission. This breaks socket backpressure,
including TSQ.
Napi increases the number of interrupts generated compared to the
current model, which keeps interrupts disabled as long as the ring
has enough free descriptors. Keep tx napi optional for now. Follow-on
patches will reduce the interrupt cost.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/net/virtio_net.c | 73 ++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 61 insertions(+), 12 deletions(-)
@@ -86,6 +88,8 @@ struct send_queue {/* Name of the send queue: output.$index */charname[40];++structnapi_structnapi;};/* Internal representation of a receive virtqueue */
@@ -262,12 +266,16 @@ static void virtqueue_napi_complete(struct napi_struct *napi,staticvoidskb_xmit_done(structvirtqueue*vq){structvirtnet_info*vi=vq->vdev->priv;+structnapi_struct*napi=&vi->sq[vq2txq(vq)].napi;/* Suppress further interrupts. */virtqueue_disable_cb(vq);-/* We were probably waiting for more output buffers. */-netif_wake_subqueue(vi->dev,vq2txq(vq));+if(napi->weight)+virtqueue_napi_schedule(napi,vq);+else+/* We were probably waiting for more output buffers. */+netif_wake_subqueue(vi->dev,vq2txq(vq));}staticunsignedintmergeable_ctx_to_buf_truesize(unsignedlongmrg_ctx)
@@ -961,6 +969,9 @@ static void skb_recv_done(struct virtqueue *rvq)staticvoidvirtnet_napi_enable(structvirtqueue*vq,structnapi_struct*napi){+if(!napi->weight)+return;+napi_enable(napi);/* If all buffers were filled by other side before we napi_enabled, we
@@ -1046,12 +1057,13 @@ static int virtnet_open(struct net_device *dev)if(!try_fill_recv(vi,&vi->rq[i],GFP_KERNEL))schedule_delayed_work(&vi->refill,0);virtnet_napi_enable(vi->rq[i].vq,&vi->rq[i].napi);+virtnet_napi_enable(vi->sq[i].vq,&vi->sq[i].napi);}return0;}-staticvoidfree_old_xmit_skbs(structsend_queue*sq)+staticunsignedintfree_old_xmit_skbs(structsend_queue*sq,intbudget){structsk_buff*skb;unsignedintlen;
@@ -1130,9 +1166,11 @@ static netdev_tx_t start_xmit(struct sk_buff *skb, struct net_device *dev)interr;structnetdev_queue*txq=netdev_get_tx_queue(dev,qnum);boolkick=!skb->xmit_more;+booluse_napi=sq->napi.weight;/* Free up any pending old buffers before queueing new ones. */-free_old_xmit_skbs(sq);+if(!use_napi)+free_old_xmit_skbs(sq,napi_weight);/* timestamp packet in software */skb_tx_timestamp(skb);
@@ -1152,8 +1190,10 @@ static netdev_tx_t start_xmit(struct sk_buff *skb, struct net_device *dev)}/* Don't wait up for transmitted skbs to be freed. */-skb_orphan(skb);-nf_reset(skb);+if(!use_napi){+skb_orphan(skb);+nf_reset(skb);+}/* If running out of space, stop queue to avoid getting packets that we*arethenunabletotransmit.
@@ -1167,9 +1207,10 @@ static netdev_tx_t start_xmit(struct sk_buff *skb, struct net_device *dev)*/if(sq->vq->num_free<2+MAX_SKB_FRAGS){netif_stop_subqueue(dev,qnum);-if(unlikely(!virtqueue_enable_cb_delayed(sq->vq))){+if(!use_napi&&+unlikely(!virtqueue_enable_cb_delayed(sq->vq))){/* More just got used, free them then recheck. */-free_old_xmit_skbs(sq);+free_old_xmit_skbs(sq,virtqueue_get_vring_size(sq->vq));if(sq->vq->num_free>=2+MAX_SKB_FRAGS){netif_start_subqueue(dev,qnum);virtqueue_disable_cb(sq->vq);
@@ -1371,8 +1412,10 @@ static int virtnet_close(struct net_device *dev)/* Make sure refill_work doesn't re-enable napi! */cancel_delayed_work_sync(&vi->refill);-for(i=0;i<vi->max_queue_pairs;i++)+for(i=0;i<vi->max_queue_pairs;i++){napi_disable(&vi->rq[i].napi);+napi_disable(&vi->sq[i].napi);+}return0;}
@@ -1741,8 +1785,10 @@ static int virtnet_restore_up(struct virtio_device *vdev)if(!try_fill_recv(vi,&vi->rq[i],GFP_KERNEL))schedule_delayed_work(&vi->refill,0);-for(i=0;i<vi->max_queue_pairs;i++)+for(i=0;i<vi->max_queue_pairs;i++){virtnet_napi_enable(vi->rq[i].vq,&vi->rq[i].napi);+virtnet_napi_enable(vi->sq[i].vq,&vi->sq[i].napi);+}}netif_device_attach(vi->dev);
@@ -1947,6 +1993,7 @@ static void virtnet_free_queues(struct virtnet_info *vi)for(i=0;i<vi->max_queue_pairs;i++){napi_hash_del(&vi->rq[i].napi);netif_napi_del(&vi->rq[i].napi);+netif_napi_del(&vi->sq[i].napi);}/* We called napi_hash_del() before netif_napi_del(),
@@ -2132,6 +2179,8 @@ static int virtnet_alloc_queues(struct virtnet_info *vi)vi->rq[i].pages=NULL;netif_napi_add(vi->dev,&vi->rq[i].napi,virtnet_poll,napi_weight);+netif_napi_add(vi->dev,&vi->sq[i].napi,virtnet_poll_tx,+napi_tx_weight);sg_init_table(vi->rq[i].sg,ARRAY_SIZE(vi->rq[i].sg));ewma_pkt_len_init(&vi->rq[i].mrg_avg_pkt_len);
From: Jason Wang <hidden> Date: 2017-03-06 09:29:56
On 2017年03月03日 22:39, Willem de Bruijn wrote:
quoted hunk
From: Willem de Bruijn <willemb@google.com>
Convert virtio-net to a standard napi tx completion path. This enables
better TCP pacing using TCP small queues and increases single stream
throughput.
The virtio-net driver currently cleans tx descriptors on transmission
of new packets in ndo_start_xmit. Latency depends on new traffic, so
is unbounded. To avoid deadlock when a socket reaches its snd limit,
packets are orphaned on tranmission. This breaks socket backpressure,
including TSQ.
Napi increases the number of interrupts generated compared to the
current model, which keeps interrupts disabled as long as the ring
has enough free descriptors. Keep tx napi optional for now. Follow-on
patches will reduce the interrupt cost.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/net/virtio_net.c | 73 ++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 61 insertions(+), 12 deletions(-)
Maybe we should use module_param for this? Or in the future, use
tx-frames-irq for a per-device configuration.
This option should eventually just go away, and napi tx become the
standard mode.
In the short term, while we evaluate it on varied workloads, a
module_param sounds good to me. In general that is frowned
upon, as it leads to different configuration interfaces for each
device driver. But that should not be a concern in this limited
case.
Maybe we should use module_param for this? Or in the future, use
tx-frames-irq for a per-device configuration.
This option should eventually just go away, and napi tx become the
standard mode.
In the short term, while we evaluate it on varied workloads, a
module_param sounds good to me. In general that is frowned
upon, as it leads to different configuration interfaces for each
device driver. But that should not be a concern in this limited
case.
In any event, do we really need a TX weight at all?
I guess you tried this, but why doesn't it not work to just do
all TX work unconditionally in a NAPI poll pass? This is how
we encourage all NIC drivers to handle this.
Maybe we should use module_param for this? Or in the future, use
tx-frames-irq for a per-device configuration.
This option should eventually just go away, and napi tx become the
standard mode.
In the short term, while we evaluate it on varied workloads, a
module_param sounds good to me. In general that is frowned
upon, as it leads to different configuration interfaces for each
device driver. But that should not be a concern in this limited
case.
In any event, do we really need a TX weight at all?
I guess you tried this, but why doesn't it not work to just do
all TX work unconditionally in a NAPI poll pass? This is how
we encourage all NIC drivers to handle this.
This seems to be more or less what this driver does already.
So I suspect it can just ignore the weight.
--
MST
Maybe we should use module_param for this? Or in the future, use
tx-frames-irq for a per-device configuration.
This option should eventually just go away, and napi tx become the
standard mode.
In the short term, while we evaluate it on varied workloads, a
module_param sounds good to me. In general that is frowned
upon, as it leads to different configuration interfaces for each
device driver. But that should not be a concern in this limited
case.
In any event, do we really need a TX weight at all?
I guess you tried this, but why doesn't it not work to just do
all TX work unconditionally in a NAPI poll pass? This is how
we encourage all NIC drivers to handle this.
This seems to be more or less what this driver does already.
So I suspect it can just ignore the weight.
Okay. Then we still need a boolean to toggle tx napi until we're
sure that the old path can be deprecated.
From: "Michael S. Tsirkin" <mst@redhat.com> Date: 2017-03-06 19:44:15
On Fri, Mar 03, 2017 at 09:39:05AM -0500, Willem de Bruijn wrote:
From: Willem de Bruijn <willemb@google.com>
Add napi for virtio-net transmit completion processing. Based on
previous patchsets by Jason Wang:
[RFC V7 PATCH 0/7] enable tx interrupts for virtio-net
http://lkml.iu.edu/hypermail/linux/kernel/1505.3/00245.html
This patchset is not ready for submission yet, but it is time for
another checkpoint. Among others, it requires more testing with
more diverse workloads.
Before commit b0c39dbdc204 ("virtio_net: don't free buffers in xmit
ring") the virtio-net driver would free transmitted packets on
transmission of new packets in ndo_start_xmit and, to catch the edge
case when no new packet is sent, also in a timer at 10HZ.
A timer can cause long stalls. VIRTIO_F_NOTIFY_ON_EMPTY avoids stalls
due to low free descriptor count. It does not address a stalls due to
low socket SO_SNDBUF. Increasing timer frequency decreases that stall
time, but increases interrupt rate and, thus, cycle count.
Currently, with no timer, packets are freed only at ndo_start_xmit.
Latency of consume_skb is now unbounded. To avoid a deadlock if a sock
reaches SO_SNDBUF, packets are orphaned on tx. This breaks TCP small
queues.
Reenable TCP small queues by removing the orphan. Instead of using a
timer, convert the driver to regular tx napi. This does not have the
unresolved stall issue and does not have any frequency to tune.
By keeping interrupts enabled by default, napi increases tx
interrupt rate. VIRTIO_F_EVENT_IDX avoids sending an interrupt if
one is already unacknowledged, so makes this more feasible today.
Combine that with two optimizations that bring interrupt rate
back in line with the existing code:
Interrupt coalescing delays interrupts until a number of events
accrue or a timer fires.
Tx completion cleaning on rx interrupts elides most explicit tx
interrupts by relying on the fact that many rx interrupts fire.
Tested by running {1, 10, 100} TCP_STREAM and TCP_RR tests from a
guest to a server on the host, on an x86_64 Haswell. The guest
runs 4 vCPUs pinned to 4 cores. vhost and the test server are
pinned to a core each.
All results are the median of 5 runs, with variance well < 10%.
Used neper (github.com/google/neper) as test process. Tests used
experimental_zcopy=0. This is likely no longer needed.
Napi increases single stream throughput, but increases cycle cost
across the board. Interrupt moderation ("+vhost") reverts both, if
not fully. For this workload with ACKs in the return path, the
last optimization ("at-rx") is more effective. For UDP this is
likely not true.
I am inclined to say coalescing is more problematic because under light
load it causes timers to fire on host, causing exits if any VM is
running on the same core. Some people might have spare cores, etc,
but generally I think at-rx might be less disruptive.
UDP testing would be required to determine how effective it is,
current numbers look nice.
upstream napi +vhost +at-rx +v+at-rx
Stream:
1x:
Mbps 30182 38782 30106 38002 32842
Gcycles 405 499 386 403 417
10x:
Mbps 40441 40575 41638 40260 41299
Gcycles 438 545 430 416 416
100x:
Mbps 34049 34697 34763 34637 34259
Gcycles 441 545 433 415 422
Latency (us):
1x:
p50 24 24 24 21 24
p99 27 27 27 26 27
Gcycles 299 430 432 312 297
10x:
p50 30 31 31 42 31
p99 40 46 48 52 42
Gcycles 347 423 471 322 463
100x:
p50 155 151 163 306 161
p99 337 329 352 361 349
Gcycles 340 421 463 306 441
Lower throughput at 100x vs 10x can be (at least in part)
explained by looking at bytes per packet sent (nstat). It likely
also explains the lower throughput of 1x for some variants.
upstream:
N=1 bytes/pkt=16581
N=10 bytes/pkt=61513
N=100 bytes/pkt=51558
at_rx:
N=1 bytes/pkt=65204
N=10 bytes/pkt=65148
N=100 bytes/pkt=56840
For this experiment, vhost has 64 frames and usecs thresholds.
Configuring this from the guest requires additional patches to qemu.
Temporary patch:
@@ -846,9 +845,6 @@ static int vhost_net_open(struct inode *inode, struct file *f)
vhost_poll_init(n->poll + VHOST_NET_VQ_TX, handle_tx_net, POLLOUT, dev);
vhost_poll_init(n->poll + VHOST_NET_VQ_RX, handle_rx_net, POLLIN, dev);
- vqs[VHOST_NET_VQ_TX]->max_coalesce_ktime = ktime_set(0, 64 * NSEC_PER_USEC);
- vqs[VHOST_NET_VQ_TX]->max_coalesce_frames = 64;
-
f->private_data = n;
TODO
- restart timer if trylock failed and lock not held by hande_tx
- start timer only at end of handle_tx and kill at start
- make napi_tx configurable
- increase test coverage
- 4KB TCP_RR
- UDP
- multithreaded sender
- with experimental_zcopytx
Willem de Bruijn (4):
virtio-net: napi helper functions
virtio-net: transmit napi
vhost: interrupt coalescing support
virtio-net: clean tx descriptors from rx napi
drivers/net/virtio_net.c | 157 +++++++++++++++++++++++++++++++++------------
drivers/vhost/vhost.c | 74 ++++++++++++++++++++-
drivers/vhost/vhost.h | 12 ++++
include/uapi/linux/vhost.h | 11 ++++
4 files changed, 211 insertions(+), 43 deletions(-)
--
2.12.0.rc1.440.g5b76565f74-goog