From: Thomas Monjalon <thomas@monjalon.net>
To: Anoob Joseph <anoobj@marvell.com>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
dev@dpdk.org, Akhil Goyal <gakhil@marvell.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Archana Muniganti <marchana@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce IPsec xform struct changes
Date: Sat, 07 Aug 2021 19:13:43 +0200 [thread overview]
Message-ID: <1778019.AoXQmIOSTh@thomas> (raw)
In-Reply-To: <CALBAE1PJTfgFT3_gtkR6iwi1WoFiz6qr9sQ+eWWA01CXK06+SQ@mail.gmail.com>
> > > > IPsec xform struct would be updated to include IPsec SA lifetime
> > > > configuration. The existing member 'esn_soft_limit' would only track
> > > > ESN. And as sequence number control is getting introduced,
> > > > 'esn_soft_limit' may not indicate the number of packets processed.
> > > > Replace that with a new structure to cover all lifetime cases with
> > > > support for specifying both soft and hard lifetimes.
> > > >
> > > > ESN control introduced by:
> > > > http://patches.dpdk.org/project/dpdk/patch/20210713133542.3550525-4-
> > > > radu.nicolau@intel.com/
> > > >
> > > > Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> > > Acked-by: Akhil Goyal <gakhil@marvell.com>
> > Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
That's a lot of acks from Marvell but looks OK.
Applied, thanks.
prev parent reply other threads:[~2021-08-07 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 6:48 [dpdk-dev] [PATCH] doc: announce IPsec xform struct changes Anoob Joseph
2021-08-04 17:01 ` Akhil Goyal
2021-08-04 17:35 ` Ananyev, Konstantin
2021-08-07 13:32 ` Jerin Jacob
2021-08-07 17:13 ` Thomas Monjalon [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=1778019.AoXQmIOSTh@thomas \
--to=thomas@monjalon.net \
--cc=anoobj@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktejasree@marvell.com \
--cc=marchana@marvell.com \
--cc=radu.nicolau@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.