netdev - Re: [PATCH net-next 00/12] tls: add support for kernel-driven resync and nfp RX offload

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 11 Jun 2019 12:22:47 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     jakub.kicinski@...ronome.com
Cc:     netdev@...r.kernel.org, oss-drivers@...ronome.com,
        alexei.starovoitov@...il.com, davejwatson@...com,
        borisp@...lanox.com
Subject: Re: [PATCH net-next 00/12] tls: add support for kernel-driven
 resync and nfp RX offload

From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Mon, 10 Jun 2019 21:39:58 -0700

> This series adds TLS RX offload for NFP and completes the offload
> by providing resync strategies.  When TLS data stream looses segments
> or experiences reorder NIC can no longer perform in line offload.
> Resyncs provide information about placement of records in the
> stream so that offload can resume.
> 
> Existing TLS resync mechanisms are not a great fit for the NFP.
> In particular the TX resync is hard to implement for packet-centric
> NICs.  This patchset adds an ability to perform TX resync in a way
> similar to the way initial sync is done - by calling down to the
> driver when new record is created after driver indicated sync had
> been lost.
> 
> Similarly on the RX side, we try to wait for a gap in the stream
> and send record information for the next record.  This works very
> well for RPC workloads which are the primary focus at this time.

Series applied, thanks Jakub.