From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Verma, Shally" <Shally.Verma@cavium.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Athreya, Narayana Prasad" <NarayanaPrasad.Athreya@cavium.com>,
"Murthy, Nidadavolu" <Nidadavolu.Murthy@cavium.com>,
"Sahu, Sunila" <Sunila.Sahu@cavium.com>,
"Gupta, Ashish" <Ashish.Gupta@cavium.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Keating, Brian A" <brian.a.keating@intel.com>,
"Griffin, John" <john.griffin@intel.com>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [RFC v1 1/1] lib/cryptodev: add support of asymmetric crypto
Date: Thu, 22 Feb 2018 10:38:39 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589325737@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <CY4PR0701MB3634B8A799FE9B465EE8AFA5F0CD0@CY4PR0701MB3634.namprd07.prod.outlook.com>
Hi Shally,
> [Shally] That's the intention but until then I assume we agree to current proposal?!
>
> If yes, then just to align and close on our discussion on this here’s the summary :
> - There's no differentiation to device capability and qp capability. If PMD shows in its feature flag that it
> supports both sym and asym then it must support those on all its qps.
> - if PMD support both but internally has hw with dedicated qp for each service then it *can* split itself
> into two: symmetric only and asymmetric only PMD instances.
> - Currently we don’t see a requirement to dedicate qp to a service, thus no need for
> max_nb_sym/asym_qp or service_type info during qp_setup. However this is open for review and
> discussion and can be added later, if any requirement is identified for same.
>
> Is that correct?
[Fiona] Yes.
next prev parent reply other threads:[~2018-02-22 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 9:54 [dpdk-dev] [RFC v1 0/1] " Shally Verma
2018-01-23 9:54 ` [dpdk-dev] [RFC v1 1/1] " Shally Verma
2018-02-01 11:36 ` [dpdk-dev] FW: " Verma, Shally
2018-02-02 15:12 ` Jain, Deepak K
2018-02-09 18:13 ` [dpdk-dev] " Trahe, Fiona
2018-02-15 5:32 ` Verma, Shally
2018-02-15 11:46 ` Trahe, Fiona
2018-02-22 5:50 ` Verma, Shally
2018-02-22 10:38 ` Trahe, Fiona [this message]
2018-03-07 12:16 ` Verma, Shally
2018-03-14 12:12 ` Trahe, Fiona
2018-03-16 8:02 ` Verma, Shally
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=348A99DA5F5B7549AA880327E580B43589325737@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=Ashish.Gupta@cavium.com \
--cc=NarayanaPrasad.Athreya@cavium.com \
--cc=Nidadavolu.Murthy@cavium.com \
--cc=Shally.Verma@cavium.com \
--cc=Sunila.Sahu@cavium.com \
--cc=brian.a.keating@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@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).