From: eperezma@redhat.com
To: bugzilla@dpdk.org, dev@dpdk.org, Maxime Coquelin <mcoqueli@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Adrian Moreno Zapata <amorenoz@redhat.com>
Subject: Re: [dpdk-dev] [Bug 383] dpdk virtio_user lack of notifications make vhost_net+napi stops tx buffers
Date: Thu, 09 Jan 2020 16:55:37 +0100 [thread overview]
Message-ID: <6d0d5484704aa5cc79f20ac94ac6103e430f712f.camel@redhat.com> (raw)
In-Reply-To: <bug-383-3@http.bugs.dpdk.org/>
Proposal for patch - Requesting For Comments.
Just running the shadow copy-flush-call unconditionally in
vhost_flush_dequeue_packed solve the issue, and it gives the best
latency I can get in the tests (8101.959 trans/sec if I run netperf
TCP_RR, 1331.735 trans/sec if I run TCP_STREAM at the same time). Apart
from that, testpmd is able to tx about 820Kpps to the guest.
However, to still do a little bit of batching I replace the condition
for the one attached here. Although it implies a read barrier, I am
able to achieve a little more of throughput (about 890Kpps), reducing
to 8048.919 the numbers of transactions/sec in TCP_RR test (1372.327 if
it runs in parallel with TCP_STREAM).
I also tried to move the vhost_flush_dequeue_shadow_packed and
host_flush_dequeue_shadow_packed after the do_data_copy_dequeue in
virtio_dev_tx_packed, more or less the same way virtio_dev_rx_packed
do, but I repeatedly find less throughput in this case, even if I add
the !next_desc_is_avail(vq) test. Not sure why, since both ways should
be very similar. About 836Kpps are achieved this way, and TCP_RR is
able to do 8120.154 trans/sec by itself and 1363.341 trans/sec if it
runs with another TCP_STREAM test in parallel.
So, is there room for improvement, either in the patches or in the
tests? Is one of the solutions preferred over another?
All tests were run with:
* producer in a different processor than consumer (host testpmd and VM
never run in the same core)
* 256 descriptors queues in guest's testpmd and tx vq
Thanks!
PS: Sorry for the from mail address change, DPDK bugzilla doesn't send
me the confirmation mail to this account.
diff --git a/lib/librte_vhost/virtio_net.c
b/lib/librte_vhost/virtio_net.c
index 21c311732..f7137149c 100644
--- a/lib/librte_vhost/virtio_net.c
+++ b/lib/librte_vhost/virtio_net.c
@@ -382,6 +382,20 @@ vhost_shadow_enqueue_single_packed(struct
virtio_net *dev,
}
}
+static __rte_always_inline bool
+next_desc_is_avail(const struct vhost_virtqueue *vq)
+{
+ bool wrap_counter = vq->avail_wrap_counter;
+ uint16_t next_used_idx = vq->last_used_idx + 1;
+
+ if (next_used_idx >= vq->size) {
+ next_used_idx -= vq->size;
+ wrap_counter ^= 1;
+ }
+
+ return desc_is_avail(&vq->desc_packed[next_used_idx],
wrap_counter);
+}
+
static __rte_always_inline void
vhost_flush_dequeue_packed(struct virtio_net *dev,
struct vhost_virtqueue *vq)
@@ -394,7 +408,8 @@ vhost_flush_dequeue_packed(struct virtio_net *dev,
if (shadow_count <= 0)
shadow_count += vq->size;
- if ((uint32_t)shadow_count >= (vq->size - MAX_PKT_BURST)) {
+ if ((uint32_t)shadow_count >= (vq->size - MAX_PKT_BURST)
+ || !next_desc_is_avail(vq)) {
do_data_copy_dequeue(vq);
vhost_flush_dequeue_shadow_packed(dev, vq);
vhost_vring_call_packed(dev, vq);
On Thu, 2020-01-09 at 15:47 +0000, bugzilla@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=383
>
> Bug ID: 383
> Summary: dpdk virtio_user lack of notifications make
> vhost_net+napi stops tx buffers
> Product: DPDK
> Version: unspecified
> Hardware: All
> OS: Linux
> Status: UNCONFIRMED
> Severity: normal
> Priority: Normal
> Component: vhost/virtio
> Assignee: dev@dpdk.org
> Reporter: eupm90@gmail.com
> Target Milestone: ---
>
> Using the current testpmd vhost_user as:
>
> ./app/testpmd -l 6,7,8 --vdev='net_vhost1,iface=/tmp/vhost-user1'
> --vdev='net_vhost2,iface=/tmp/vhost-user2' -- -a -i --rxq=1 --txq=1
> --txd=1024
> --forward-mode=rxonly
>
> And starting qemu using packed=on on the interface:
>
> -netdev vhost-user,chardev=charnet1,id=hostnet1 -device
> virtio-net-pci,rx_queue_size=256,...,packed=on
>
> And start to tx in the guest using:
>
> ./dpdk/build/app/testpmd -l 1,2 --vdev=eth_af_packet0,iface=eth0 -- \
> --forward-mode=txonly --txq=1 --txd=256 --auto-start --txpkts
> 1500 \
> --stats-period 1
>
> After first burst of packets (512 or a little more), sendto() will
> start to
> return EBUSY. kernel NAPI is refusing to send more packets to
> virtio_net device
> until it free old skbs.
>
> However, virtio_net driver is unable to free old buffers since host
> does not return them in `vhost_flush_dequeue_packed` until shadow
> queue is full
> except for MAX_PKT_BURST (32) packets.
>
> Sometimes we are lucky and reach this point, or packets are small
> enough to
> fill the queue and flush, but if the packets and the virtqueue are
> big enough,
> we will not be able to tx anymore.
>
next prev parent reply other threads:[~2020-01-09 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 15:47 bugzilla
2020-01-09 15:55 ` eperezma [this message]
2020-01-15 7:05 ` Liu, Yong
2020-01-29 19:33 ` [dpdk-dev] [PATCH] vhost: flush shadow tx if there is no more packets Eugenio Pérez
2020-01-31 18:38 ` Kevin Traynor
2020-02-04 9:23 ` Eugenio Perez Martin
2020-02-04 13:48 ` Kevin Traynor
2020-02-04 15:05 ` Eugenio Perez Martin
2020-02-04 15:10 ` Maxime Coquelin
2020-02-05 9:09 ` Maxime Coquelin
2020-02-05 9:47 ` Maxime Coquelin
2020-02-05 15:45 ` Eugenio Perez Martin
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=6d0d5484704aa5cc79f20ac94ac6103e430f712f.camel@redhat.com \
--to=eperezma@redhat.com \
--cc=amorenoz@redhat.com \
--cc=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
--cc=jasowang@redhat.com \
--cc=mcoqueli@redhat.com \
--cc=mst@redhat.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 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).