From: Jerin Jacob <jerinjacobk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
dpdk-dev <dev@dpdk.org>,
"Akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"pathreya@marvell.com" <pathreya@marvell.com>,
"pkapoor@marvell.com" <pkapoor@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: update for armv8 crypto library
Date: Wed, 23 Oct 2019 13:42:16 +0530 [thread overview]
Message-ID: <CALBAE1Nci4Dq2JQnntJWFJ46iSehQoTBB2JTa5cg-MrVqvL2qg@mail.gmail.com> (raw)
In-Reply-To: <3373803.DCgnikpo0B@xps>
On Wed, Oct 23, 2019 at 11:53 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 23/10/2019 04:50, Jerin Jacob:
> > In past, there was a concern with this approach about maintaining the
> > assembly code in dpdk.org. Is this concern still valid?
> [...]
> > DPDK does not define any such interface. It was pushed to external library
> > for the reason mentioned above.
>
> Yes it is questionable to host some asm code which is doing a processing
> not really specific to DPDK.
Currently, it is doing the DPDK specific processing like kernel code
as asm code.
> Also, my first thought was that this library could be used by other projects.
OK.
> Another concern about integrating this crypto lib in DPDK is to know
> whether it would have an impact on DPDK packaging and delivering?
See below.
> I don't remember any answer about legal export of this crypto processing.
I don't think, we ran through the legal check on this.
But this can be a genuine issue from the above list. Not sure how
Linux kernel handles this case.
>
>
next prev parent reply other threads:[~2019-10-23 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 7:34 jerinj
2019-10-16 11:35 ` Jerin Jacob
2019-10-22 20:32 ` Honnappa Nagarahalli
2019-10-23 2:50 ` Jerin Jacob
2019-10-23 6:23 ` Thomas Monjalon
2019-10-23 8:12 ` Jerin Jacob [this message]
2019-10-23 17:11 ` Honnappa Nagarahalli
2019-10-23 17:28 ` Jerin Jacob
2019-10-23 18:17 ` Honnappa Nagarahalli
2019-10-24 11:36 ` Ferruh Yigit
2019-10-23 17:41 ` Jerin Jacob
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=CALBAE1Nci4Dq2JQnntJWFJ46iSehQoTBB2JTa5cg-MrVqvL2qg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=pathreya@marvell.com \
--cc=pkapoor@marvell.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).