vhost: Make iotlb mempool not single-consumer
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
- v2 Latest1 patch 3 repliesApplied
- v11 patch 6 repliesSuperseded
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | vhost: fix iotlb mempool single-consumer flaglib/ | +1 | 3 replies |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | Chenbo Xia | Maxime Coquelin |
|---|---|---|
| 1/1 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
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