Skip to content

vhost: Make iotlb mempool not single-consumer

Eugenio Pérez dpdk-dev 2 versions – Applied

Status from this message: Applied to dpdk-next-virtio/master.

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest1 patch 3 repliesApplied
  2. v11 patch 6 repliesSuperseded

Patches in v2 Applied

#Subject and filesSizeRepliesApplied
1/1vhost: fix iotlb mempool single-consumer flaglib/librte_vhost/iotlb.c+1 -23 replies

Reviews trailers per patch

The patch has a Reviewed-by or Acked-by.

PatchChenbo XiaMaxime Coquelin
1/1R-b R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [dpdk-dev] [PATCH v2 0/1] vhost: Make iotlb mempool not single-consumer

Bugzilla bug: 523

This behavior is only observed on packed vq + virtio-net kernel driver in the guest, so we could make the single-consumer flag optional. However, I have not found why I cannot see the issue in split, so the safer option is to never set it.

Any comments?

Thanks!

v2: Modify commit message to not to include all trace and commands.

Eugenio Pérez (1):
vhost: fix iotlb mempool single-consumer flag

 lib/librte_vhost/iotlb.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
Signature · 1 line
2.18.1