From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Jiang, Cheng1" <cheng1.jiang@intel.com>, <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: <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] app/dma-perf: introduce dma-perf application
Date: Mon, 19 Sep 2022 10:19:47 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87333@smartserver.smartshare.dk> (raw)
In-Reply-To: <SN7PR11MB7019FF3CD3162E912B408291DC4D9@SN7PR11MB7019.namprd11.prod.outlook.com>
> From: Jiang, Cheng1 [mailto:cheng1.jiang@intel.com]
> Sent: Monday, 19 September 2022 10.10
>
> > From: Morten Brørup <mb@smartsharesystems.com>
> > Sent: Friday, September 16, 2022 3:36 PM
> >
> > > From: Cheng Jiang [mailto:cheng1.jiang@intel.com]
> > > Sent: Thursday, 15 September 2022 17.48
[...]
> > Is there any reason for making this a separate application, instead
> of part of
> > the /app/test/ application?
>
> >
> > NB: Someone could have asked the same question about test-compress-
> dev
> > and similar applications... ;-)
>
> First of all, this application is specifically used to test the
> performance of DMA device, and does not involve functional testing.
> So I'm not sure whether it is suitable for the app/test.
Good point.
> Secondly, the configuration and switching of many test scenarios are
> involved here, so we think it may be a more appropriate to be an
> independent application.
Makes sense to me. The independent application might provide more flexibility.
>
> >
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
>
> Thanks for your acknowledgement.
> Cheng
next prev parent reply other threads:[~2022-09-19 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 15:47 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 [this message]
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
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=98CBD80474FA8B44BF855DF32C47DC35D87333@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=cheng1.jiang@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.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).