From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: David Marchand <david.marchand@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Wan Junjie <wanjunjie@bytedance.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Peng He <hepeng.0320@bytedance.com>,
Zhihong Wang <wangzhihong.wzh@bytedance.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] vhost: avoid iotlb mempool allocation while IOMMU disabled
Date: Thu, 13 May 2021 10:24:03 +0000 [thread overview]
Message-ID: <MN2PR11MB40633FC52AC3E2EBF14BAC7B9C519@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8x+JtDt6gaom-wuMz+DqZvQiZER8v_waW1RnoV7Cr8gUg@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, May 13, 2021 4:39 PM
> To: Xia, Chenbo <chenbo.xia@intel.com>; Maxime Coquelin
> <maxime.coquelin@redhat.com>
> Cc: Wan Junjie <wanjunjie@bytedance.com>; dev@dpdk.org; Peng He
> <hepeng.0320@bytedance.com>; Zhihong Wang <wangzhihong.wzh@bytedance.com>
> 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 <chenbo.xia@intel.com> wrote:
> >
> > > -----Original Message-----
> > > From: Wan Junjie <wanjunjie@bytedance.com>
> > > Sent: Tuesday, February 2, 2021 4:15 PM
> > > To: Xia, Chenbo <chenbo.xia@intel.com>; Maxime Coquelin
> > > <maxime.coquelin@redhat.com>
> > > Cc: dev@dpdk.org; Wan Junjie <wanjunjie@bytedance.com>; Peng He
> > > <hepeng.0320@bytedance.com>; Zhihong Wang <wangzhihong.wzh@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.0320@bytedance.com>
> > > Signed-off-by: Wan Junjie <wanjunjie@bytedance.com>
> > > Reviewed-by: Zhihong Wang <wangzhihong.wzh@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
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
next prev parent reply other threads:[~2021-05-13 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 8:14 Wan Junjie
2021-04-07 7:10 ` Xia, Chenbo
2021-05-13 8:39 ` David Marchand
2021-05-13 10:24 ` Xia, Chenbo [this message]
2021-05-13 10:51 ` [dpdk-dev] [External] " Wan Junjie
2021-05-13 10:58 ` Xia, Chenbo
2021-05-13 11:41 ` Xia, Chenbo
-- strict thread matches above, loose matches on Subject: below --
2021-01-29 16:39 [dpdk-dev] [PATCH] " Wan Junjie
2021-02-02 8:38 ` [dpdk-dev] [PATCH v2] " Wan Junjie
2021-02-03 2:26 ` Xia, Chenbo
2021-02-03 16:49 ` Maxime Coquelin
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=MN2PR11MB40633FC52AC3E2EBF14BAC7B9C519@MN2PR11MB4063.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hepeng.0320@bytedance.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).