DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Anoob Joseph <anoobj@marvell.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Narayana Prasad Raju Athreya <pathreya@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Fan Zhang <roy.fan.zhang@intel.com>,
	Fiona Trahe <fiona.trahe@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] doc: add inline protocol in feature list
Date: Wed, 12 Feb 2020 14:10:32 +0000	[thread overview]
Message-ID: <VE1PR04MB6639FAA950728556F3AE8B9BE61B0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <949441fe-160d-ceaf-e264-c0e69303e52d@intel.com>


> On 2/12/2020 1:48 PM, Akhil Goyal wrote:
> > Hi Ferruh,
> >>
> >>
> >> Since both using the rte_security, for a PMD isn't there a way to say if it is
> >> supporting any one of them or both? If so what do you think documenting it
> too?
> >>
> > I think that is mentioned in the rte_security capabilities about the action types
> > Which are supported by the driver. One of the dev->security_ctx->ops is to get
> the security
> > Capabilities which will return the supported action type by the PMD.
> >
> > I am not sure if we can add that here or not. It is your call.
> >
> 
> I think it make sense to document action types needs to be supported to claim
> that the feature is supported, but most probably you will judge better on the
> matter.

If we can add specifics of security in ethernet feature definition,
Then probably we can add 
**[provides]   rte_security_ops, capabilities_get**: `` action: RTE_SECURITY_ACTION_TYPE_INLINE_CRYPTO ``

For inline crypto
And
**[provides]   rte_security_ops, capabilities_get**: `` action: RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL`` 

Please check my syntax if it is not correct.



  reply	other threads:[~2020-02-12 14:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  6:53 [dpdk-dev] " Anoob Joseph
2020-01-21  5:40 ` Anoob Joseph
2020-01-21 16:12   ` Ferruh Yigit
2020-01-22  9:47     ` [dpdk-dev] [EXT] " Anoob Joseph
2020-02-04 14:35       ` Ferruh Yigit
2020-02-10  5:44         ` Anoob Joseph
2020-02-12 10:25           ` Akhil Goyal
2020-02-12 13:30             ` Ferruh Yigit
2020-02-12 13:48               ` Akhil Goyal
2020-02-12 13:53                 ` Ferruh Yigit
2020-02-12 14:10                   ` Akhil Goyal [this message]
2020-02-17 15:22 ` [dpdk-dev] [PATCH v2] " Anoob Joseph
2020-02-17 15:39   ` [dpdk-dev] [PATCH v3] " Anoob Joseph
2020-02-18  7:40     ` Akhil Goyal
2020-02-18  9:28       ` Ferruh Yigit
2020-02-18 10:02         ` Ferruh Yigit

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=VE1PR04MB6639FAA950728556F3AE8B9BE61B0@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=pathreya@marvell.com \
    --cc=roy.fan.zhang@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).