From: "Michael S. Tsirkin" <mst@redhat.com>
To: wexu@redhat.com
Cc: mjrosato@linux.vnet.ibm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net,stable] vhost: fix skb leak in handle_rx()
Date: Tue, 28 Nov 2017 19:53:33 +0200 [thread overview]
Message-ID: <20171128195140-mutt-send-email-mst__41619.9188483462$1511891622$gmane$org@kernel.org> (raw)
In-Reply-To: <1511889436-12876-1-git-send-email-wexu@redhat.com>
On Tue, Nov 28, 2017 at 12:17:16PM -0500, wexu@redhat.com wrote:
> From: Wei Xu <wexu@redhat.com>
>
> Matthew found a roughly 40% tcp throughput regression with commit
> c67df11f(vhost_net: try batch dequing from skb array) as discussed
> in the following thread:
> https://www.mail-archive.com/netdev@vger.kernel.org/msg187936.html
>
> Eventually we figured out that it was a skb leak in handle_rx()
> when sending packets to the VM. This usually happens when a guest
> can not drain out vq as fast as vhost fills in, afterwards it sets
> off the traffic jam and leaks skb(s) which occurs as no headcount
> to send on the vq from vhost side.
>
> This can be avoided by making sure we have got enough headcount
> before actually consuming a skb from the batched rx array while
> transmitting, which is simply done by deferring it a moment later
> in this patch.
>
> Signed-off-by: Wei Xu <wexu@redhat.com>
Given the amount of effort Matthew has put into this,
you definitely want
Reported-by: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
here.
Let's give credit where credit is due.
Thanks a lot Matthew!
> ---
> drivers/vhost/net.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> index 8d626d7..e76535e 100644
> --- a/drivers/vhost/net.c
> +++ b/drivers/vhost/net.c
> @@ -778,8 +778,6 @@ static void handle_rx(struct vhost_net *net)
> /* On error, stop handling until the next kick. */
> if (unlikely(headcount < 0))
> goto out;
> - if (nvq->rx_array)
> - msg.msg_control = vhost_net_buf_consume(&nvq->rxq);
> /* On overrun, truncate and discard */
> if (unlikely(headcount > UIO_MAXIOV)) {
> iov_iter_init(&msg.msg_iter, READ, vq->iov, 1, 1);
> @@ -809,6 +807,8 @@ static void handle_rx(struct vhost_net *net)
> */
> iov_iter_advance(&msg.msg_iter, vhost_hlen);
> }
> + if (nvq->rx_array)
> + msg.msg_control = vhost_net_buf_consume(&nvq->rxq);
> err = sock->ops->recvmsg(sock, &msg,
> sock_len, MSG_DONTWAIT | MSG_TRUNC);
> /* Userspace might have consumed the packet meanwhile:
> --
> 1.8.3.1
next prev parent reply other threads:[~2017-11-28 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1511889436-12876-1-git-send-email-wexu@redhat.com>
2017-11-28 17:50 ` [PATCH net,stable] vhost: fix skb leak in handle_rx() Michael S. Tsirkin
2017-11-29 6:12 ` Wei Xu
2017-11-28 17:53 ` Michael S. Tsirkin [this message]
2017-11-29 1:53 ` Jason Wang
[not found] ` <9b234fdd-baa3-f919-6c72-f6768265f1ca@redhat.com>
2017-11-29 5:06 ` Jason Wang
[not found] ` <37f16bef-4a59-b895-c61b-e3f473617411@redhat.com>
2017-11-29 5:44 ` Wei Xu
[not found] ` <20171128195140-mutt-send-email-mst@kernel.org>
2017-11-29 6:32 ` Wei Xu
2017-11-28 17:17 wexu
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='20171128195140-mutt-send-email-mst__41619.9188483462$1511891622$gmane$org@kernel.org' \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@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).