On Fri, 2019-10-18 at 18:51 -0700, Jakub Kicinski wrote:
> On Fri, 18 Oct 2019 19:38:24 +0000, Saeed Mahameed wrote:
> > From: Tariq Toukan <tar...@mellanox.com>
> >
> > Once the kTLS TX resync function is called, it used to return
> > a binary value, for success or failure.
> >
> > However, in case the TLS SKB is a retransmission of the connection
> > handshake, it initiates the resync flow (as the tcp seq check
> > holds),
> > while regular packet handle is expected.
> >
> > In this patch, we identify this case and skip the resync operation
> > accordingly.
> >
> > Counters:
> > - Add a counter (tls_skip_no_sync_data) to monitor this.
> > - Bump the dump counters up as they are used more frequently.
> > - Add a missing counter descriptor declaration for tls_resync_bytes
> > in sq_stats_desc.
> >
> > Fixes: d2ead1f360e8 ("net/mlx5e: Add kTLS TX HW offload support")
> > Signed-off-by: Tariq Toukan <tar...@mellanox.com>
> > Signed-off-by: Saeed Mahameed <sae...@mellanox.com>
>
> Could you document the new counter in tls-offload.rst?
Tariq already prepared the patch, do we want this in net or net-next ?
most of our kTLS users are going to use 5.3/5.4 stable kernels, but i
am not sure this should go to net..
Thanks,
Saeed.
