On Wed, Apr 7, 2021 at 9:10 AM Xia, Chenbo <chenbo....@intel.com> wrote: > > > -----Original Message----- > > From: Wan Junjie <wanjun...@bytedance.com> > > Sent: Tuesday, February 2, 2021 4:15 PM > > To: Xia, Chenbo <chenbo....@intel.com>; Maxime Coquelin > > <maxime.coque...@redhat.com> > > Cc: dev@dpdk.org; Wan Junjie <wanjun...@bytedance.com>; Peng He > > <hepeng.0...@bytedance.com>; Zhihong Wang <wangzhihong....@bytedance.com> > > Subject: [PATCH v2] vhost: avoid iotlb mempool allocation while IOMMU > > disabled > > > > If vhost device's IOMMU feature is disabled, iotlb mempool allocation > > is unnecessary. > > > > Reported-by: Peng He <hepeng.0...@bytedance.com> > > Signed-off-by: Wan Junjie <wanjun...@bytedance.com> > > Reviewed-by: Zhihong Wang <wangzhihong....@bytedance.com> > > --- > > 2.11.0 > > Patch applied to next-virtio/main with conflict resolved, Thanks
This patch triggered a regression reported by Red Hat QE. https://bugs.dpdk.org/show_bug.cgi?id=703 Reverting the patch is enough to fix the regression. I'll let you guys decide on the next step for 21.05. -- David Marchand
