> -----Original Message----- > From: David Marchand <[email protected]> > Sent: Thursday, May 13, 2021 4:39 PM > To: Xia, Chenbo <[email protected]>; Maxime Coquelin > <[email protected]> > Cc: Wan Junjie <[email protected]>; [email protected]; Peng He > <[email protected]>; Zhihong Wang <[email protected]> > Subject: Re: [dpdk-dev] [PATCH v2] vhost: avoid iotlb mempool allocation while > IOMMU disabled > > On Wed, Apr 7, 2021 at 9:10 AM Xia, Chenbo <[email protected]> wrote: > > > > > -----Original Message----- > > > From: Wan Junjie <[email protected]> > > > Sent: Tuesday, February 2, 2021 4:15 PM > > > To: Xia, Chenbo <[email protected]>; Maxime Coquelin > > > <[email protected]> > > > Cc: [email protected]; Wan Junjie <[email protected]>; Peng He > > > <[email protected]>; Zhihong Wang <[email protected]> > > > 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 <[email protected]> > > > Signed-off-by: Wan Junjie <[email protected]> > > > Reviewed-by: Zhihong Wang <[email protected]> > > > --- > > > 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
I cannot reproduce this issue on my machine. @Wan Junjie Could you reproduce this? I prefer to revert the patch if things are not very clear as it is only a minor optimization. Thanks, Chenbo
