DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	nd <nd@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] Armv8_crypto PMD future.
Date: Tue, 22 Oct 2019 20:19:26 +0000	[thread overview]
Message-ID: <VE1PR08MB5149A68339B9BFE915715C6C98680@VE1PR08MB5149.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <VE1PR04MB6639F7E5F0DA16D92EE6A80CE6680@VE1PR04MB6639.eurprd04.prod.outlook.com>

Thanks Akhil for helping make progress on this discussion.

From: Akhil Goyal <akhil.goyal@nxp.com> 
Sent: Tuesday, October 22, 2019 6:03 AM
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: dev@dpdk.org; hemant.agrawal@nxp.com; jerinj@marvell.com; thomas@monjalon.net
Subject: Armv8_crypto PMD future.

Hi Honnappa,

As per the comments received in
http://patches.dpdk.org/patch/60499/
http://patches.dpdk.org/patch/61013/

Marvell will no longer host the external library for the PMD.
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.

Please send your suggestions/concerns.
Since this library provide huge performance improvements over conventional
Openssl. We should not remove it altogether.
We should find a way to host it somewhere.

Regards,
Akhil


  reply	other threads:[~2019-10-22 20: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 [this message]
2019-10-23  6:40   ` Thomas Monjalon
2019-10-23 14:32     ` Honnappa Nagarahalli
2019-10-23 17:19       ` Honnappa Nagarahalli

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=VE1PR08MB5149A68339B9BFE915715C6C98680@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).