jazune

> Yes, supporting OpenSSL would be very nice. There are two obstacles to it: > > 1. It is not high on our priority list. > 2. OpenSSL does not...

@dtikhonov I plan only change lsquic code that will be suitable for both boringssl and openssl with quic sdk patch. So, it won't effect current compile. And If one want...

hi @Yogaraj-Alamenda Thank you for your reply. My driver version is 4.4.0, using USDM, and my qat_engine version is v0.5.38. I have 2 8960 cards, qat_service status: There are 6...

hi @Yogaraj-Alamenda ，I compile the libqat.so with the -fno-omit-frame-pointer option，and I get the function of the perf。It seems the lock happend in qat_rsa_priv_enc。 

hi ,@Yogaraj-Alamenda: I am now sure the lock or the bottleneck is in memory pool manager in qat from the perf. There are 3 files may be used in qat...

hi @Yogaraj-Alamenda Thank you for your reply. The perf file is attached, and accoding to the perf, I think the qat mem manager is the bottleneck. We only test individual...

hi @Yogaraj-Alamenda In my matchine, the perf show up the symbols.  q2 : qat engine use v0.38, what about driver version? 1.6 or 1.7? q3: We try to set...

hi @Yogaraj-Alamenda I use the contig mem instread of usdm, and change one line code of multi_thread_qaememutils.c static __thread int crypto_inited = 0; now I can get max performace ....

Hi @Yogaraj-Alamenda , thanks for the clarification! Can you answer another issue about multi-thread for me？ Thank you very much.