From: "Michael S. Tsirkin" <mst@redhat.com>
To: wangyunjian <wangyunjian@huawei.com>
Cc: netdev@vger.kernel.org, jasowang@redhat.com,
willemdebruijn.kernel@gmail.com,
virtualization@lists.linux-foundation.org,
jerry.lilijun@huawei.com, chenchanghu@huawei.com,
xudingke@huawei.com, brian.huangbin@huawei.com
Subject: Re: [PATCH net v2 2/2] vhost_net: fix high cpu load when sendmsg fails
Date: Wed, 16 Dec 2020 04:23:16 -0500 [thread overview]
Message-ID: <20201216042027-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <6b4c5fff8705dc4b5b6a25a45c50f36349350c73.1608065644.git.wangyunjian@huawei.com>
On Wed, Dec 16, 2020 at 04:20:37PM +0800, wangyunjian wrote:
> From: Yunjian Wang <wangyunjian@huawei.com>
>
> Currently we break the loop and wake up the vhost_worker when
> sendmsg fails. When the worker wakes up again, we'll meet the
> same error. This will cause high CPU load. To fix this issue,
> we can skip this description by ignoring the error. When we
> exceeds sndbuf, the return value of sendmsg is -EAGAIN. In
> the case we don't skip the description and don't drop packet.
Question: with this patch, what happens if sendmsg is interrupted by a signal?
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> ---
> drivers/vhost/net.c | 21 +++++++++------------
> 1 file changed, 9 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> index c8784dfafdd7..3d33f3183abe 100644
> --- a/drivers/vhost/net.c
> +++ b/drivers/vhost/net.c
> @@ -827,16 +827,13 @@ static void handle_tx_copy(struct vhost_net *net, struct socket *sock)
> msg.msg_flags &= ~MSG_MORE;
> }
>
> - /* TODO: Check specific error and bomb out unless ENOBUFS? */
> err = sock->ops->sendmsg(sock, &msg, len);
> - if (unlikely(err < 0)) {
> + if (unlikely(err == -EAGAIN)) {
> vhost_discard_vq_desc(vq, 1);
> vhost_net_enable_vq(net, vq);
> break;
> - }
> - if (err != len)
> - pr_debug("Truncated TX packet: len %d != %zd\n",
> - err, len);
> + } else if (unlikely(err != len))
> + vq_err(vq, "Fail to sending packets err : %d, len : %zd\n", err, len);
> done:
> vq->heads[nvq->done_idx].id = cpu_to_vhost32(vq, head);
> vq->heads[nvq->done_idx].len = 0;
> @@ -922,7 +919,6 @@ static void handle_tx_zerocopy(struct vhost_net *net, struct socket *sock)
> msg.msg_flags &= ~MSG_MORE;
> }
>
> - /* TODO: Check specific error and bomb out unless ENOBUFS? */
> err = sock->ops->sendmsg(sock, &msg, len);
> if (unlikely(err < 0)) {
> if (zcopy_used) {
> @@ -931,13 +927,14 @@ static void handle_tx_zerocopy(struct vhost_net *net, struct socket *sock)
> nvq->upend_idx = ((unsigned)nvq->upend_idx - 1)
> % UIO_MAXIOV;
> }
> - vhost_discard_vq_desc(vq, 1);
> - vhost_net_enable_vq(net, vq);
> - break;
> + if (err == -EAGAIN) {
> + vhost_discard_vq_desc(vq, 1);
> + vhost_net_enable_vq(net, vq);
> + break;
> + }
> }
> if (err != len)
> - pr_debug("Truncated TX packet: "
> - " len %d != %zd\n", err, len);
> + vq_err(vq, "Fail to sending packets err : %d, len : %zd\n", err, len);
I'd rather make the pr_debug -> vq_err a separate change, with proper
commit log describing motivation.
> if (!zcopy_used)
> vhost_add_used_and_signal(&net->dev, vq, head, 0);
> else
> --
> 2.23.0
next prev parent reply other threads:[~2020-12-16 9:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 1:48 [PATCH net 0/2] fixes for vhost_net wangyunjian
2020-12-15 1:48 ` [PATCH net 1/2] vhost_net: fix ubuf refcount incorrectly when sendmsg fails wangyunjian
2020-12-15 2:45 ` Willem de Bruijn
2020-12-15 7:51 ` wangyunjian
2020-12-15 1:48 ` [PATCH net 2/2] vhost_net: fix high cpu load " wangyunjian
2020-12-15 4:09 ` Jason Wang
2020-12-15 8:03 ` wangyunjian
2020-12-16 5:56 ` Jason Wang
2020-12-16 7:43 ` wangyunjian
2020-12-16 7:47 ` Jason Wang
2020-12-16 8:20 ` [PATCH net v2 0/2] fixes for vhost_net wangyunjian
2020-12-16 8:20 ` [PATCH net v2 1/2] vhost_net: fix ubuf refcount incorrectly when sendmsg fails wangyunjian
2020-12-16 14:17 ` Willem de Bruijn
2020-12-16 20:56 ` Michael S. Tsirkin
2020-12-16 8:20 ` [PATCH net v2 2/2] vhost_net: fix high cpu load " wangyunjian
2020-12-16 9:23 ` Michael S. Tsirkin [this message]
2020-12-17 2:38 ` wangyunjian
2020-12-17 3:19 ` Jason Wang
2020-12-21 23:07 ` Willem de Bruijn
2020-12-22 4:41 ` Jason Wang
2020-12-22 14:24 ` Willem de Bruijn
2020-12-23 2:53 ` Jason Wang
2020-12-23 13:21 ` wangyunjian
2020-12-23 13:48 ` Willem de Bruijn
2020-12-23 2:46 ` wangyunjian
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=20201216042027-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=brian.huangbin@huawei.com \
--cc=chenchanghu@huawei.com \
--cc=jasowang@redhat.com \
--cc=jerry.lilijun@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wangyunjian@huawei.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xudingke@huawei.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).