From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>
Cc: "Akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] Armv8_crypto PMD future.
Date: Wed, 23 Oct 2019 17:19:07 +0000 [thread overview]
Message-ID: <VE1PR08MB51498F24CCC414B40774D87A986B0@VE1PR08MB5149.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <VE1PR08MB5149F93860DFA33633B1ECA5986B0@VE1PR08MB5149.eurprd08.prod.outlook.com>
> <snip>
>
> >
> > 22/10/2019 22:19, Honnappa Nagarahalli:
> > > From: Akhil Goyal <akhil.goyal@nxp.com>
> > > > We can have 2 possible solutions to this situation
> > > >
> > > > 1. Arm host it somewhere and let people contribute to that.
> > > > 2. Integrate it inside DPDK repo.
> > >
> > > [Honnappa] I don't have any issues with the 2nd option.
> >
> > So you want this code to be part of the PMD?
> I have asked similar question in the patch email. If it is moving to DPDK, where
> in DPDK?
>
> > You think no other project would like to use such crypto code?
> I would say it depends on the library and what it offers. I definitely think it will
> be useful for other projects when it is fully developed. This is just my view, may
> be others have a different opinion. I believe we (Arm community) are trying to
> find a solution for the current problem. The solution can be a short term
> solution.
>
> > What are the export restrictions for this code?
> I am aware of the export restrictions around crypto code in general. I am not
> sure about these restrictions in DPDK's context.
Can this be a 'hosted-project' (like pktgen, NFF-Go etc)? Are the 'hosted-projects' also subjected to export restrictions?
>
> I have a question here. If the library was broken (in whatever way) and nobody
> asked it to be fixed, I am wondering if it is getting used by anyone.
>
> >
> >
prev parent reply other threads:[~2019-10-23 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 11:02 Akhil Goyal
2019-10-22 20:19 ` Honnappa Nagarahalli
2019-10-23 6:40 ` Thomas Monjalon
2019-10-23 14:32 ` Honnappa Nagarahalli
2019-10-23 17:19 ` Honnappa Nagarahalli [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=VE1PR08MB51498F24CCC414B40774D87A986B0@VE1PR08MB5149.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=thomas@monjalon.net \
/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).