From: "Jiang, Cheng1" <cheng1.jiang@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"mb@smartsharesystems.com" <mb@smartsharesystems.com>,
"dev@dpdk.org" <dev@dpdk.org>, "Hu, Jiayu" <jiayu.hu@intel.com>,
"Ding, Xuan" <xuan.ding@intel.com>,
"Ma, WenwuX" <wenwux.ma@intel.com>,
"Wang, YuanX" <yuanx.wang@intel.com>,
"Yang, YvonneX" <yvonnex.yang@intel.com>,
"He, Xingguang" <xingguang.he@intel.com>
Subject: RE: [RFC v3] app/dma-perf: introduce dma-perf application
Date: Tue, 25 Oct 2022 02:17:39 +0000 [thread overview]
Message-ID: <SN7PR11MB7019140E8DB079EB0428FB79DC319@SN7PR11MB7019.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8x5=bTa9T4b=wGtUZNGj7B2uTCS2Z-0ha7JLd=v53iFqg@mail.gmail.com>
Sure, I'll take a look and fix them in the next version.
Thanks,
Cheng
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Friday, October 21, 2022 9:29 PM
> To: Jiang, Cheng1 <cheng1.jiang@intel.com>
> Cc: thomas@monjalon.net; Richardson, Bruce
> <bruce.richardson@intel.com>; mb@smartsharesystems.com;
> dev@dpdk.org; Hu, Jiayu <jiayu.hu@intel.com>; Ding, Xuan
> <xuan.ding@intel.com>; Ma, WenwuX <wenwux.ma@intel.com>; Wang,
> YuanX <yuanx.wang@intel.com>; Yang, YvonneX
> <yvonnex.yang@intel.com>; He, Xingguang <xingguang.he@intel.com>
> Subject: Re: [RFC v3] app/dma-perf: introduce dma-perf application
>
> On Tue, Oct 18, 2022 at 9:22 AM Cheng Jiang <cheng1.jiang@intel.com>
> wrote:
> >
> > There are many high-performance DMA devices supported in DPDK now,
> and
> > these DMA devices can also be integrated into other modules of DPDK as
> > accelerators, such as Vhost. Before integrating DMA into applications,
> > developers need to know the performance of these DMA devices in
> > various scenarios and the performance of CPUs in the same scenario,
> > such as different buffer lengths. Only in this way can we know the
> > target performance of the application accelerated by using them. This
> > patch introduces a high-performance testing tool, which supports
> > comparing the performance of CPU and DMA in different scenarios
> > automatically with a pre-set config file. Memory Copy performance test are
> supported for now.
> >
> > Signed-off-by: Cheng Jiang <cheng1.jiang@intel.com>
> > Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
> > Signed-off-by: Yuan Wang <yuanx.wang@intel.com>
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
> > ---
> > v3: improved nr_buf calculation and added support for getting
> > subprocess exit status
> > v2: fixed some CI issues.
>
> There is still at least one build issue.
>
>
> --
> David Marchand
next prev parent reply other threads:[~2022-10-25 2:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 15:47 [RFC] " Cheng Jiang
2022-09-16 7:36 ` Morten Brørup
2022-09-19 8:09 ` Jiang, Cheng1
2022-09-19 8:19 ` Morten Brørup
2022-09-19 11:39 ` [RFC v2] " Cheng Jiang
2022-10-18 6:42 ` [RFC v3] " Cheng Jiang
2022-10-21 13:28 ` David Marchand
2022-10-25 2:17 ` Jiang, Cheng1 [this message]
2022-10-25 4:34 ` [RFC v4] " Cheng Jiang
2022-10-25 5:19 ` [RFC v5] " Cheng Jiang
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=SN7PR11MB7019140E8DB079EB0428FB79DC319@SN7PR11MB7019.namprd11.prod.outlook.com \
--to=cheng1.jiang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=mb@smartsharesystems.com \
--cc=thomas@monjalon.net \
--cc=wenwux.ma@intel.com \
--cc=xingguang.he@intel.com \
--cc=xuan.ding@intel.com \
--cc=yuanx.wang@intel.com \
--cc=yvonnex.yang@intel.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).