From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Sivaprasad Tummala <Sivaprasad.Tummala@intel.com>,
Zhihong Wang <zhihong.wang@intel.com>,
Xiaolong Ye <xiaolong.ye@intel.com>
Cc: dev@dpdk.org, Flavio Leitner <fbl@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v1] vhost: fix mbuf allocation failures
Date: Wed, 29 Apr 2020 10:43:01 +0200 [thread overview]
Message-ID: <020fd369-6b44-c5fe-c7b1-e33146de4c37@redhat.com> (raw)
In-Reply-To: <20200428095203.64935-1-Sivaprasad.Tummala@intel.com>
Hi Sivaprasad,
On 4/28/20 11:52 AM, Sivaprasad Tummala wrote:
> vhost buffer allocation is successful for packets that fit
> into a linear buffer. If it fails, vhost library is expected
> to drop the current buffer descriptor and skip to the next.
>
> The patch fixes the error scenario by skipping to next descriptor.
> Note: Drop counters are not currently supported.
Fixes tag is missing here, and stable@dpdk.org should be cc'ed if
necessary.
> Signed-off-by: Sivaprasad Tummala <Sivaprasad.Tummala@intel.com>
> ---
> lib/librte_vhost/virtio_net.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_vhost/virtio_net.c b/lib/librte_vhost/virtio_net.c
> index 37c47c7dc..b0d3a85c2 100644
> --- a/lib/librte_vhost/virtio_net.c
> +++ b/lib/librte_vhost/virtio_net.c
> @@ -1688,6 +1688,7 @@ virtio_dev_tx_split(struct virtio_net *dev, struct vhost_virtqueue *vq,
> {
You only fix split ring path, but not packed ring.
> uint16_t i;
> uint16_t free_entries;
> + uint16_t dropped = 0;
>
> if (unlikely(dev->dequeue_zero_copy)) {
> struct zcopy_mbuf *zmbuf, *next;
> @@ -1751,8 +1752,19 @@ virtio_dev_tx_split(struct virtio_net *dev, struct vhost_virtqueue *vq,
> update_shadow_used_ring_split(vq, head_idx, 0);
>
> pkts[i] = virtio_dev_pktmbuf_alloc(dev, mbuf_pool, buf_len);
> - if (unlikely(pkts[i] == NULL))
> + if (unlikely(pkts[i] == NULL)) {
> + /*
> + * mbuf allocation fails for jumbo packets with
> + * linear buffer flag set. Drop this packet and
> + * proceed with the next available descriptor to
> + * avoid HOL blocking
> + */
> + VHOST_LOG_DATA(WARNING,
> + "Failed to allocate memory for mbuf. Packet dropped!\n");
I think we need a better logging, otherwise it is going to flood the log
file quite rapidly if issue happens. Either some rate-limited logging or
warn-once would be better.
The warning message could be also improved, because when using linear
buffers, one would expect that the size of the mbufs could handle a
jumbo frame. So it should differentiate two
> + dropped += 1;
> + i++;
> break;
> + }
>
> err = copy_desc_to_mbuf(dev, vq, buf_vec, nr_vec, pkts[i],
> mbuf_pool);
> @@ -1796,7 +1808,7 @@ virtio_dev_tx_split(struct virtio_net *dev, struct vhost_virtqueue *vq,
> }
> }
>
> - return i;
> + return (i - dropped);
> }
>
> static __rte_always_inline int
>
next prev parent reply other threads:[~2020-04-29 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 9:52 Sivaprasad Tummala
2020-04-29 8:43 ` Maxime Coquelin [this message]
2020-04-29 17:35 ` Flavio Leitner
2020-04-30 7:13 ` Tummala, Sivaprasad
2020-05-04 17:11 ` [dpdk-dev] [PATCH v2] vhost: fix mbuf alloc failure Sivaprasad Tummala
2020-05-04 19:32 ` Flavio Leitner
2020-05-05 5:48 ` Tummala, Sivaprasad
2020-05-05 8:20 ` Maxime Coquelin
2020-05-05 11:56 ` Tummala, Sivaprasad
2020-05-08 11:17 ` [dpdk-dev] [PATCH v3] vhost: fix mbuf allocation failures Sivaprasad Tummala
2020-05-15 7:29 ` Maxime Coquelin
2020-05-15 8:36 ` Maxime Coquelin
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=020fd369-6b44-c5fe-c7b1-e33146de4c37@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=Sivaprasad.Tummala@intel.com \
--cc=dev@dpdk.org \
--cc=fbl@redhat.com \
--cc=xiaolong.ye@intel.com \
--cc=zhihong.wang@intel.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).