From: Akhil Goyal <akhil.goyal@nxp.com>
To: Praveen Shetty <praveen.shetty@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"anoobj@marvell.com" <anoobj@marvell.com>
Cc: "bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v6] examples/ipsec-secgw: support flow director feature
Date: Fri, 17 Apr 2020 20:58:04 +0000 [thread overview]
Message-ID: <VI1PR04MB3168AF6EFEA380AE222585EBE6D90@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200416164729.43051-1-praveen.shetty@intel.com>
>
> Support load distribution in security gateway application using
> NIC load distribution feature(Flow Director).
> Flow Director is used to redirect the specified inbound ipsec flow
> to a specified queue.This is achieved by extending the SA rule syntax
> to support specification by adding new action_type of <flow-direction>
> to a specified <port_id> <queue_id>.
>
> Signed-off-by: Praveen Shetty <praveen.shetty@intel.com>
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
> ---
> v6 changes:
> Incorporated all the review comments from Akhil on v5.
>
> doc/guides/rel_notes/release_20_05.rst | 4 +-
> doc/guides/sample_app_ug/ipsec_secgw.rst | 16 ++++++
> examples/ipsec-secgw/ep0.cfg | 11 ++++
> examples/ipsec-secgw/ipsec-secgw.c | 22 ++++++++
> examples/ipsec-secgw/ipsec.c | 66 ++++++++++++++++++++++++
> examples/ipsec-secgw/ipsec.h | 7 +++
> examples/ipsec-secgw/sa.c | 65 +++++++++++++++++++++--
> 7 files changed, 186 insertions(+), 5 deletions(-)
>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2020-04-17 20:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 14:55 [dpdk-dev] [PATCH v1] " Praveen Shetty
2020-03-12 11:00 ` Anoob Joseph
[not found] ` <BN7PR11MB25310A9A6B9C3BE91A411AA29DFD0@BN7PR11MB2531.namprd11.prod.outlook.com>
[not found] ` <BN7PR11MB2531E92F9B078563A947615F9DFD0@BN7PR11MB2531.namprd11.prod.outlook.com>
[not found] ` <BN7PR11MB2531ABDDAE26D1FD3B216E259DFD0@BN7PR11MB2531.namprd11.prod.outlook.com>
2020-03-13 7:05 ` Shetty, Praveen
2020-03-13 10:51 ` Anoob Joseph
2020-03-13 12:21 ` Shetty, Praveen
2020-03-19 16:21 ` [dpdk-dev] [PATCH v2] " Praveen Shetty
2020-03-20 8:15 ` Anoob Joseph
2020-03-23 11:24 ` Shetty, Praveen
2020-03-31 13:02 ` [dpdk-dev] [PATCH v3] " Praveen Shetty
2020-04-01 13:19 ` Akhil Goyal
2020-04-01 13:26 ` Anoob Joseph
2020-04-01 13:53 ` Akhil Goyal
2020-04-02 11:15 ` Shetty, Praveen
2020-04-02 13:39 ` [dpdk-dev] [EXT] " Anoob Joseph
2020-04-02 17:56 ` Shetty, Praveen
2020-04-03 5:14 ` Anoob Joseph
2020-04-03 5:52 ` Akhil Goyal
2020-04-03 10:21 ` Shetty, Praveen
2020-04-03 10:28 ` Anoob Joseph
2020-04-08 14:13 ` [dpdk-dev] [PATCH v4] " Praveen Shetty
2020-04-09 10:09 ` [dpdk-dev] [PATCH v5] " Praveen Shetty
2020-04-14 7:33 ` Shetty, Praveen
2020-04-15 18:59 ` Akhil Goyal
2020-04-16 11:49 ` Shetty, Praveen
2020-04-16 16:47 ` [dpdk-dev] [PATCH v6] " Praveen Shetty
2020-04-17 20:58 ` Akhil Goyal [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=VI1PR04MB3168AF6EFEA380AE222585EBE6D90@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=bernard.iremonger@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=praveen.shetty@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).