From: Leon Romanovsky <leon@kernel.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH net-next 3/3] nfp: implement xfrm callbacks and expose ipsec offload feature to upper layer
Date: Wed, 7 Sep 2022 21:06:30 +0300 [thread overview]
Message-ID: <Yxjdpt42BAiZe0sK@unreal> (raw)
In-Reply-To: <20220907094758.35571-4-simon.horman@corigine.com>
On Wed, Sep 07, 2022 at 11:47:58AM +0200, Simon Horman wrote:
> From: Huanhuan Wang <huanhuan.wang@corigine.com>
>
> Xfrm callbacks are implemented to offload SA info into firmware
> by mailbox. It supports 16K SA info in total.
>
> Expose ipsec offload feature to upper layer, this feature will
> signal the availability of the offload.
>
> Based on initial work of Norm Bagley <norman.bagley@netronome.com>.
>
> Signed-off-by: Huanhuan Wang <huanhuan.wang@corigine.com>
> Reviewed-by: Louis Peens <louis.peens@corigine.com>
> Signed-off-by: Simon Horman <simon.horman@corigine.com>
> ---
> .../net/ethernet/netronome/nfp/crypto/ipsec.c | 552 +++++++++++++++++-
> .../ethernet/netronome/nfp/nfp_net_common.c | 6 +
> .../net/ethernet/netronome/nfp/nfp_net_ctrl.h | 4 +-
> 3 files changed, 558 insertions(+), 4 deletions(-)
<...>
> + if (x->props.flags & XFRM_STATE_ESN)
> + cfg->ctrl_word.ext_seq = 1;
> + else
> + cfg->ctrl_word.ext_seq = 0;
Don't you need to implement xdo_dev_state_advance_esn() too?
Thanks
next prev parent reply other threads:[~2022-09-07 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 9:47 [PATCH net-next 0/3] nfp: IPsec offload support Simon Horman
2022-09-07 9:47 ` [PATCH net-next 1/3] nfp: extend capability and control words Simon Horman
2022-09-07 9:47 ` [PATCH net-next 2/3] nfp: add framework to support ipsec offloading Simon Horman
2022-09-07 9:47 ` [PATCH net-next 3/3] nfp: implement xfrm callbacks and expose ipsec offload feature to upper layer Simon Horman
2022-09-07 18:06 ` Leon Romanovsky [this message]
2022-09-14 3:10 ` Yinjun Zhang
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=Yxjdpt42BAiZe0sK@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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).