From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Hu, Jiayu" <jiayu.hu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
"Jiang, Cheng1" <cheng1.jiang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: remove copy threshold for async vhost
Date: Thu, 16 Sep 2021 11:55:07 +0000 [thread overview]
Message-ID: <MN2PR11MB40639B8DB4A421F1E83827AD9CDC9@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c9671896-4cb0-52b5-b47d-ab7e4dcc606a@redhat.com>
Hi,
> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Thursday, September 16, 2021 7:34 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Hu, Jiayu <jiayu.hu@intel.com>;
> dev@dpdk.org
> Cc: Xia, Chenbo <chenbo.xia@intel.com>; david.marchand@redhat.com; Jiang,
> Cheng1 <cheng1.jiang@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] vhost: remove copy threshold for async vhost
>
> Hi Ferruh,
>
> On 9/16/21 13:15, Ferruh Yigit wrote:
> > On 8/20/2021 1:44 PM, Jiayu Hu wrote:
> >> Copy threshold is introduced in async vhost data path to select
> >> the appropriate copy engine to do copies for higher efficiency.
> >> However, it may cause packets out-of-order, and it also causes
> >> data path performance unpredictable.
> >>
> >
> > Just checking, if the patch is fixing data performance issue, should it be
> > backported?
>
> This is experimental code that is not used in real product for now, and
> will likely heavily change given OVS rejected this design.
>
> So I would personally not bother backporting patches for it.
+1. Based on the experimental state. Let's save the effort of backporting.
Thanks,
Chenbo
> Jiayu, Chenbo, do you think otherwise?
>
> Regards,
> Maxime
>
> >> Therefore, this patch removes copy threshold support in async vhost
> >> data path.
> >>
> >> Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
> >> Signed-off-by: Cheng Jiang <cheng1.jiang@intel.com>
> > <...>
> >
> >
prev parent reply other threads:[~2021-09-16 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 12:44 Jiayu Hu
2021-08-27 8:20 ` Maxime Coquelin
2021-09-14 11:24 ` Maxime Coquelin
2021-09-16 11:15 ` Ferruh Yigit
2021-09-16 11:34 ` Maxime Coquelin
2021-09-16 11:55 ` Xia, Chenbo [this message]
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=MN2PR11MB40639B8DB4A421F1E83827AD9CDC9@MN2PR11MB4063.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=cheng1.jiang@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jiayu.hu@intel.com \
--cc=maxime.coquelin@redhat.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).