[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae89bba7-2541-e994-41da-fb791ced7aa7@gmail.com>
Date: Wed, 9 Dec 2020 20:39:28 -0700
From: David Ahern <dsahern@...il.com>
To: Boris Pismenny <borispismenny@...il.com>,
Boris Pismenny <borisp@...lanox.com>, kuba@...nel.org,
davem@...emloft.net, saeedm@...dia.com, hch@....de,
sagi@...mberg.me, axboe@...com, kbusch@...nel.org,
viro@...iv.linux.org.uk, edumazet@...gle.com
Cc: boris.pismenny@...il.com, linux-nvme@...ts.infradead.org,
netdev@...r.kernel.org, benishay@...dia.com, ogerlitz@...dia.com,
yorayz@...dia.com
Subject: Re: [PATCH v1 net-next 04/15] net/tls: expose get_netdev_for_sock
On 12/9/20 12:41 AM, Boris Pismenny wrote:
>
> You are correct, and bond support is currently under review for TLS,
> i.e., search for "TLS TX HW offload for Bond". The same approach that
ok, missed that.
> is applied there is relevant here. More generally, this offload is
> very similar in concept to TLS offload (tls_device).
>
I disagree with the TLS comparison. As an example, AIUI the TLS offload
works with userspace sockets, and it is a protocol offload.
Powered by blists - more mailing lists