From: Leon Romanovsky <leon@kernel•org>
To: Steffen Klassert <steffen.klassert@secunet•com>
Cc: "David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Herbert Xu <herbert@gondor•apana.org.au>,
Jakub Kicinski <kuba@kernel•org>,
netdev@vger•kernel.org, Paolo Abeni <pabeni@redhat•com>,
Raed Salem <raeds@nvidia•com>, Saeed Mahameed <saeedm@nvidia•com>,
Bharat Bhushan <bbhushan2@marvell•com>
Subject: Re: [PATCH RFC xfrm-next v3 7/8] xfrm: add support to HW update soft and hard limits
Date: Mon, 26 Sep 2022 09:07:31 +0300 [thread overview]
Message-ID: <YzFBozQTGVbmKcwN@unreal> (raw)
In-Reply-To: <20220925092006.GT2602992@gauss3.secunet.de>
On Sun, Sep 25, 2022 at 11:20:06AM +0200, Steffen Klassert wrote:
> On Sun, Sep 04, 2022 at 04:15:41PM +0300, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia•com>
> >
> > Both in RX and TX, the traffic that performs IPsec full offload
> > transformation is accounted by HW. It is needed to properly handle
> > hard limits that require to drop the packet.
> >
> > It means that XFRM core needs to update internal counters with the one
> > that accounted by the HW, so new callbacks are introduced in this patch.
> >
> > In case of soft or hard limit is occurred, the driver should call to
> > xfrm_state_check_expire() that will perform key rekeying exactly as
> > done by XFRM core.
> >
> > Signed-off-by: Leon Romanovsky <leonro@nvidia•com>
>
> This looks good, thanks!
>
> We need this for the other relevant counters too.
It is in my backlog.
Thanks
next prev parent reply other threads:[~2022-09-26 6:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 13:15 [PATCH RFC xfrm-next v3 0/8] Extend XFRM core to allow full offload configuration Leon Romanovsky
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 1/8] xfrm: add new full offload flag Leon Romanovsky
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 2/8] xfrm: allow state full offload mode Leon Romanovsky
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 3/8] xfrm: add an interface to offload policy Leon Romanovsky
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 4/8] xfrm: add TX datapath support for IPsec full offload mode Leon Romanovsky
2022-09-25 9:16 ` Steffen Klassert
2022-09-26 6:06 ` Leon Romanovsky
2022-09-27 5:04 ` Steffen Klassert
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 5/8] xfrm: add RX datapath protection " Leon Romanovsky
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 6/8] xfrm: enforce separation between priorities of HW/SW policies Leon Romanovsky
2022-09-25 9:34 ` Steffen Klassert
2022-09-26 6:38 ` Leon Romanovsky
2022-09-27 5:48 ` Steffen Klassert
2022-09-27 10:21 ` Leon Romanovsky
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 7/8] xfrm: add support to HW update soft and hard limits Leon Romanovsky
2022-09-25 9:20 ` Steffen Klassert
2022-09-26 6:07 ` Leon Romanovsky [this message]
2022-09-27 5:49 ` Steffen Klassert
2022-09-04 13:15 ` [PATCH RFC xfrm-next v3 8/8] xfrm: document IPsec full offload mode Leon Romanovsky
2022-09-04 13:19 ` [PATCH RFC xfrm-next v3 0/8] Extend XFRM core to allow full offload configuration Leon Romanovsky
2022-09-08 9:56 ` Leon Romanovsky
2022-09-21 14:59 ` Jakub Kicinski
2022-09-21 17:37 ` Leon Romanovsky
2022-09-25 9:40 ` Steffen Klassert
2022-09-26 6:55 ` Leon Romanovsky
2022-09-27 5:59 ` Steffen Klassert
2022-09-27 10:02 ` Leon Romanovsky
2022-09-19 9:31 ` Leon Romanovsky
2022-09-22 7:17 ` Leon Romanovsky
2022-09-22 7:35 ` Steffen Klassert
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=YzFBozQTGVbmKcwN@unreal \
--to=leon@kernel$(echo .)org \
--cc=bbhushan2@marvell$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=raeds@nvidia$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=steffen.klassert@secunet$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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