I truly appreciate all the answers. Makes sense!!
Most of my background is from systems where reducing (or even eliminating)
memory copy by the CPU was the holy grail (using RDMA and other such
techniques). I do realize that compared to all the other overheads in the
network and OpenSSL path, we ca
do you just think this is the case?
> Consider that SSL_write/read will normally do something like AES or
> Chapoly on your CPU at a throughput of 2-4 GB/s, which is about an order
> of magnitude slower than streaming memory throughput.
>
> -Marian
>
> Am 02.02.20 um 15:27 schri
Hi all,
I am in the process of integrating OpenSSL with my application. My
application uses scatter-gather unencrypted buffers. Without OpenSSL, I
would use writev with no issues. Is there a way to do the equivalent over
OpenSSL? I understand that I can split the vector into multiple
SSL_write/SSL_
t; > From: Eran Borovik [mailto:eran.boro...@gmail.com]
> > Sent: Wednesday, January 29, 2020 07:32
>
> Please respond to the list rather than directly to me, since the subject
> may be of interest to other readers. I'm including the list in this
> response.
>
> &
Hi all,
My application is using non-blocking sockets to send and receive data. To
avoid issues, my code guarantees that a specific socket is always owned by
a specific thread, thus preventing any issues or races from concurrently
running send and receive at the same time on the same socket.
I've re
