From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: tiwei.bie@intel.com, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] vhost: prevent disabled rings to be processed with zero-copy
Date: Thu, 21 Mar 2019 10:11:35 +0100 [thread overview]
Message-ID: <96c409db-537a-f55f-5e36-79f2e350427a@redhat.com> (raw)
Message-ID: <20190321091135.XiNW2XAeIu9DLVxRNWsRA6R4aERO8_CF6S6EATSHQTs@z> (raw)
In-Reply-To: <20190228175704.27948-1-maxime.coquelin@redhat.com>
On 2/28/19 6:57 PM, Maxime Coquelin wrote:
> The vhost-user spec says that once the vring is disabled, the
> client has to stop processing it. But it can happen when
> dequeue zero-copy is enabled if outstanding descriptors buffers
> are still being processed by an external NIC or another guest.
>
> The fix consists in draining the zmbufs list to ensure no more
> descriptors buffers are in the wild.
>
> Note that this fix is only working in the case REPLY_ACK
> protocol feature is enabled, which is not the case by default
> for now (it is only enabled when IOMMU feature is enabled in
> the vhost library).
>
> Fixes: b0a985d1f340 ("vhost: add dequeue zero copy")
> Cc: stable@dpdk.org
>
> Reviewed-by: Tiwei Bie <tiwei.bie@intel.com>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> lib/librte_vhost/vhost_user.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/lib/librte_vhost/vhost_user.c b/lib/librte_vhost/vhost_user.c
> index 36c0c676d..555d09ad9 100644
> --- a/lib/librte_vhost/vhost_user.c
> +++ b/lib/librte_vhost/vhost_user.c
> @@ -1345,6 +1345,10 @@ vhost_user_set_vring_enable(struct virtio_net **pdev,
> dev->notify_ops->vring_state_changed(dev->vid,
> index, enable);
>
> + /* On disable, rings have to be stopped being processed. */
> + if (!enable && dev->dequeue_zero_copy)
> + drain_zmbuf_list(dev->virtqueue[index]);
> +
> dev->virtqueue[index]->enabled = enable;
>
> return RTE_VHOST_MSG_RESULT_OK;
>
Applied to dpdk-next-virtio/master.
Maxime
next prev parent reply other threads:[~2019-03-21 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 17:57 Maxime Coquelin
2019-03-21 9:11 ` Maxime Coquelin [this message]
2019-03-21 9:11 ` 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=96c409db-537a-f55f-5e36-79f2e350427a@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=tiwei.bie@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).