From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Nicolau, Radu" <radu.nicolau@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
Akhil Goyal <gakhil@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] examples/ipsec-secgw: fix ESN setting
Date: Tue, 14 Jun 2022 15:43:54 +0000 [thread overview]
Message-ID: <MW5PR11MB5809EC39E29DC94F7CFC4ACAB8AA9@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220614124313.1562369-1-radu.nicolau@intel.com>
> -----Original Message-----
> From: Radu Nicolau <radu.nicolau@intel.com>
> Sent: Tuesday, June 14, 2022 1:43 PM
> To: Nicolau, Radu <radu.nicolau@intel.com>; Akhil Goyal <gakhil@marvell.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: [PATCH] examples/ipsec-secgw: fix ESN setting
>
> Fix ESN option flag and initial value for the rte_ipsec library path.
>
> Fixes: 560029d5cfc9 ("examples/ipsec-secgw: define initial ESN value")
> Cc: stable@dpdk.org
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
> examples/ipsec-secgw/sa.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/examples/ipsec-secgw/sa.c b/examples/ipsec-secgw/sa.c
> index 0b27f11fc0..8505a676ef 100644
> --- a/examples/ipsec-secgw/sa.c
> +++ b/examples/ipsec-secgw/sa.c
> @@ -1488,6 +1488,11 @@ fill_ipsec_sa_prm(struct rte_ipsec_sa_prm *prm,
> const struct ipsec_sa *ss,
> prm->ipsec_xform.options.ecn = 1;
> prm->ipsec_xform.options.copy_dscp = 1;
>
> + if (ss->esn > 0) {
> + prm->ipsec_xform.options.esn = 1;
> + prm->ipsec_xform.esn.value = ss->esn;
> + }
> +
> if (IS_IP4_TUNNEL(ss->flags)) {
> prm->ipsec_xform.tunnel.type =
> RTE_SECURITY_IPSEC_TUNNEL_IPV4;
> prm->tun.hdr_len = sizeof(*v4);
> --
> 2.25.1
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-06-14 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 12:43 Radu Nicolau
2022-06-14 15:43 ` Zhang, Roy Fan [this message]
2022-06-15 15:11 ` Akhil Goyal
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=MW5PR11MB5809EC39E29DC94F7CFC4ACAB8AA9@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
/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).