[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191004.140724.479420933444301576.davem@davemloft.net>
Date: Fri, 04 Oct 2019 14:07:24 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jakub.kicinski@...ronome.com
Cc: netdev@...r.kernel.org, oss-drivers@...ronome.com,
davejwatson@...com, borisp@...lanox.com, aviadye@...lanox.com,
john.fastabend@...il.com, daniel@...earbox.net,
atul.gupta@...lsio.com
Subject: Re: [PATCH net-next 0/6] net/tls: separate the TLS TOE code out
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Thu, 3 Oct 2019 11:18:53 -0700
> We have 3 modes of operation of TLS - software, crypto offload
> (Mellanox, Netronome) and TCP Offload Engine-based (Chelsio).
> The last one takes over the socket, like any TOE would, and
> is not really compatible with how we want to do things in the
> networking stack.
>
> Confusingly the name of the crypto-only offload mode is TLS_HW,
> while TOE-offload related functions use tls_hw_ as their prefix.
>
> Engineers looking to implement offload are also be faced with
> TOE artefacts like struct tls_device (while, again,
> CONFIG_TLS_DEVICE actually gates the non-TOE offload).
>
> To improve the clarity of the offload code move the TOE code
> into new files, and rename the functions and structures
> appropriately.
>
> Because TOE-offload takes over the socket, and makes no use of
> the TLS infrastructure in the kernel, the rest of the code
> (anything beyond the ULP setup handlers) do not have to worry
> about the mode == TLS_HW_RECORD case.
>
> The increase in code size is due to duplication of the full
> license boilerplate. Unfortunately original author (Dave Watson)
> seems unreachable :(
Series applied.
Powered by blists - more mailing lists