From: Thomas Monjalon <thomas@monjalon.net>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"techboard@dpdk.org" <techboard@dpdk.org>,
Anoob Joseph <anoobj@marvell.com>,
"Somalapuram, Amaranath" <Amaranath.Somalapuram@amd.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
Nagadheeraj Rottela <rnagadheeraj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/5] app: add multi process crypto application
Date: Wed, 15 Jul 2020 22:20:54 +0200 [thread overview]
Message-ID: <1741506.OIoGGINOQb@thomas> (raw)
In-Reply-To: <VI1PR04MB31687D34F04FFAEFF8E9A040E67E0@VI1PR04MB3168.eurprd04.prod.outlook.com>
15/07/2020 22:15, Akhil Goyal:
> > > I see this application as a useful tool to test the readiness of a driver to be
> > used
> > > in a multi process environment. If app is not a correct place to host it, should it
> > be
> > > added in examples/multi_process/. I also suggested that in v2 but it makes
> > more
> > > sense in app as it is a unit test application which does not have any relevance
> > as
> > > standalone application as crypto may not be used standalone without ethernet
> > > for multi process scenario.
> > > My first preference was to modify l2fwd-crypto to be used as a multi process
> > proof
> > > Application but it also make sense to have a unit test application to verify
> > standalone
> > > crypto PMDs.
> > > Open for comments from other crypto PMD owners.
> >
> > I agree it looks like unit tests.
> > Can it be added to app/test/test_cryptodev* ?
> >
>
> Running two instances of test application will be a challenge I guess.
> If it can be done, I think all the cases covered in test app other than crypto would
> be affected/tested.
Right
> Test-crypto-perf can be a better option but it may defeat the purpose of test-crypto-perf.
> Best would be to make l2fwd-crypto compliant with multi process.
Yes, probably a good idea.
> But still I am ok to have a unit test application.
next prev parent reply other threads:[~2020-07-15 20:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 15:50 Arek Kusztal
2020-07-15 15:50 ` [dpdk-dev] [PATCH v3 1/5] app: add muli " Arek Kusztal
2020-07-15 15:50 ` [dpdk-dev] [PATCH v3 2/5] app/mp_crypto: add device configuration functions Arek Kusztal
2020-07-15 15:50 ` [dpdk-dev] [PATCH v3 3/5] app/mp_crypto: add function to allocatie mempools Arek Kusztal
2020-07-15 15:50 ` [dpdk-dev] [PATCH v3 4/5] app/mp_crypto: add enqueue-dequeue functions Arek Kusztal
2020-07-15 15:50 ` [dpdk-dev] [PATCH v3 5/5] doc: add documentation for multi process crypto app Arek Kusztal
2020-07-15 18:22 ` Akhil Goyal
2020-07-22 14:20 ` Kusztal, ArkadiuszX
2020-07-23 8:45 ` Akhil Goyal
2020-07-15 18:26 ` [dpdk-dev] [PATCH v3 0/5] app: add multi process crypto application Akhil Goyal
2020-07-15 19:11 ` Thomas Monjalon
2020-07-15 19:25 ` Akhil Goyal
2020-07-15 20:06 ` Thomas Monjalon
2020-07-15 20:15 ` Akhil Goyal
2020-07-15 20:20 ` Thomas Monjalon [this message]
2020-08-31 11:50 ` Kusztal, ArkadiuszX
2020-10-08 13:16 ` Kusztal, ArkadiuszX
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=1741506.OIoGGINOQb@thomas \
--to=thomas@monjalon.net \
--cc=Amaranath.Somalapuram@amd.com \
--cc=adwivedi@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=rnagadheeraj@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=techboard@dpdk.org \
/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).