DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Zhihong Wang <wangzhihong.wzh@bytedance.com>,
	Junjie Wan <wanjunjie@bytedance.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: restore IOTLB mempool allocation
Date: Mon, 17 May 2021 13:06:59 +0000	[thread overview]
Message-ID: <MN2PR11MB4063AFEFABE2F2A2DB4479279C2D9@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210517085951.28970-1-david.marchand@redhat.com>

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday, May 17, 2021 5:00 PM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; Yigit, Ferruh <ferruh.yigit@intel.com>; Maxime
> Coquelin <maxime.coquelin@redhat.com>; Xia, Chenbo <chenbo.xia@intel.com>;
> Zhihong Wang <wangzhihong.wzh@bytedance.com>; Junjie Wan
> <wanjunjie@bytedance.com>
> Subject: [PATCH] vhost: restore IOTLB mempool allocation
> 
> As explained by Chenbo, IOTLB messages will be sent when some queues
> are not enabled. If we initialize IOTLB in vhost_user_set_vring_num,
> it could happen that IOTLB update comes when IOTLB pool of disabled
> queues are not initialized.
> 
> Fixes: 968bbc7e2e50 ("vhost: avoid IOTLB mempool allocation while IOMMU
> disabled")
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> Summary of a discussion with Maxime:
> 
> To keep the mempool allocation optimization, we could try to initialise
> the per-vring mempools at reception of the first IOTLB message.
> Since those pools are used as caches, it is not an issue if some vrings
> received more IOTLB updates than others.
> 
> But looking/testing this now is too late for 21.05, hence reverting is
> the safer.
> 
> ---
>  lib/vhost/vhost.c      | 5 +++--
>  lib/vhost/vhost_user.c | 6 +-----
>  2 files changed, 4 insertions(+), 7 deletions(-)
> 
> diff --git a/lib/vhost/vhost.c b/lib/vhost/vhost.c
> index 9cbcf650b6..c96f6335c8 100644
> --- a/lib/vhost/vhost.c
> +++ b/lib/vhost/vhost.c
> @@ -365,8 +365,7 @@ free_vq(struct virtio_net *dev, struct vhost_virtqueue
> *vq)
> 
>  	vhost_free_async_mem(vq);
>  	rte_free(vq->batch_copy_elems);
> -	if (vq->iotlb_pool)
> -		rte_mempool_free(vq->iotlb_pool);
> +	rte_mempool_free(vq->iotlb_pool);
>  	rte_free(vq->log_cache);
>  	rte_free(vq);
>  }
> @@ -570,6 +569,8 @@ init_vring_queue(struct virtio_net *dev, uint32_t
> vring_idx)
>  	vq->kickfd = VIRTIO_UNINITIALIZED_EVENTFD;
>  	vq->callfd = VIRTIO_UNINITIALIZED_EVENTFD;
>  	vq->notif_enable = VIRTIO_UNINITIALIZED_NOTIF;
> +
> +	vhost_user_iotlb_init(dev, vring_idx);
>  }
> 
>  static void
> diff --git a/lib/vhost/vhost_user.c b/lib/vhost/vhost_user.c
> index 611ff209e3..8f0eba6412 100644
> --- a/lib/vhost/vhost_user.c
> +++ b/lib/vhost/vhost_user.c
> @@ -469,10 +469,6 @@ vhost_user_set_vring_num(struct virtio_net **pdev,
>  		return RTE_VHOST_MSG_RESULT_ERR;
>  	}
> 
> -	if (dev->features & (1ULL << VIRTIO_F_IOMMU_PLATFORM)) {
> -		if (vhost_user_iotlb_init(dev, msg->payload.state.index))
> -			return RTE_VHOST_MSG_RESULT_ERR;
> -	}
>  	return RTE_VHOST_MSG_RESULT_OK;
>  }
> 
> @@ -578,7 +574,7 @@ numa_realloc(struct virtio_net *dev, int index)
>  	dev->virtqueue[index] = vq;
>  	vhost_devices[dev->vid] = dev;
> 
> -	if (old_vq != vq && (dev->features & (1ULL <<
> VIRTIO_F_IOMMU_PLATFORM)))
> +	if (old_vq != vq)
>  		vhost_user_iotlb_init(dev, index);
> 
>  	return dev;
> --
> 2.23.0

Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>

  reply	other threads:[~2021-05-17 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  8:59 David Marchand
2021-05-17 13:06 ` Xia, Chenbo [this message]
2021-05-18  8:08 ` Xia, Chenbo

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=MN2PR11MB4063AFEFABE2F2A2DB4479279C2D9@MN2PR11MB4063.namprd11.prod.outlook.com \
    --to=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=wangzhihong.wzh@bytedance.com \
    --cc=wanjunjie@bytedance.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).