You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -286,6 +286,10 @@ wolfSSL Server Benchmark 16384 bytes
286
286
287
287
## Change Log
288
288
289
+
### wolfSSL Async Release v5.6.4 (Oct 30, 2023)
290
+
* Fixes for support async with crypto or pk callbacks.
291
+
* Rename `WC_NOT_PENDING_E` -> `WC_NO_PENDING_E`
292
+
289
293
### wolfSSL Async Release v5.6.3 (June 16, 2023)
290
294
* Includes all wolfSSL v5.6.3 fixes. See ChangeLog.md here: https://github.com/wolfSSL/wolfssl/blob/master/ChangeLog.md#wolfssl-release-563-jun-16-2023
291
295
* Add sanity check of index devId before accessing array
Copy file name to clipboardExpand all lines: wolfcrypt/src/port/intel/README.md
+30-57Lines changed: 30 additions & 57 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Intel QuickAssist Adapter Asynchronous Support
2
2
3
-
The wolfSSL / wolfCrypt libraries support hardware crypto acceleration using the Intel QuickAssist adapter. This software has been tested using QAT 1.6 in user space on Cent OS (Kernel 3.10.0-327.22.2.el7.x86_64) on an Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz. Intel QuickAssist is DH895xCC (BDF=03:00.0, Stepping A0, device 0 is SKU2).
3
+
The wolfSSL / wolfCrypt libraries support hardware crypto acceleration using the Intel QuickAssist adapter. This software has been tested using the Intel DH8970 and DH8950 QuickAssist adapters.
4
4
5
5
## Overview
6
6
@@ -13,33 +13,30 @@ The asynchronous crypto files are located at `wolfcrypt/src/async.c` and `wolfss
13
13
14
14
## Building
15
15
16
-
QuickAssist drivers can be downloaded from Intel here:
Note: If you have the older driver installed you may need to remove it or unload the module and reboot.
20
+
* If you have the older driver installed you may need to remove it or unload the module and reboot.
21
+
* If you are using the QAT hardware hashing, you may need to disable the params checking, which doesn't support a last partial with 0 length source input. Code runs and works, but parameter checking will fail.
22
+
Use `./configure --disable-param-check && sudo make install`
23
+
* If you want to use legacy algorithms like RSA 1024 bit then Use `./configure --enable-legacy-algorithms`
24
+
* Recommend not using `make -j` due to synchronization issues on dependencies.
28
25
29
-
1. Setup `QAT1.7` and `wolfssl` next to each other in the same folder.
26
+
3. Setup `QAT` and `wolfssl` next to each other in the same folder.
If you are using the QAT hardware hashing, you may need to disable the params checking, which doesn't support a last partial with 0 length source input. Code runs and works, but parameter checking will fail.
60
-
Use `./configure --disable-param-check && sudo make install`
Running wolfCrypt test and benchmark must be done with `sudo` to allow hardware access. By default the QuickAssist code uses the "SSL" process name via `QAT_PROCESS_NAME` in quickassist.h to match up to the hardware configuration.
95
68
96
-
Note: `sudo make check` will fail since default QAT configuration doesn't allow multiple concurrent processes to use hardware. You can run each of the make check scripts individually with sudo. The hardware configuration can be customized by editing the `QAT1.6/build/dh895xcc_qa_dev0.conf` file to allow multiple processes.
69
+
Note: `sudo make check` will fail since default QAT configuration doesn't allow multiple concurrent processes to use hardware. You can run each of the make check scripts individually with sudo. The hardware configuration can be customized by editing the `QAT/build/dh895xcc_qa_dev0.conf` file to allow multiple processes.
97
70
98
71
Here are some build options for tuning your use:
99
72
@@ -113,18 +86,18 @@ The QuickAssist v1.6 driver uses its own memory management system in `quickassis
113
86
1.`USE_QAE_STATIC_MEM`: Uses a global pool for the list of allocations. This improves performance, but consumes extra up front memory. The pre-allocation size can be tuned using `QAE_USER_MEM_MAX_COUNT`.
114
87
2.`USE_QAE_THREAD_LS` : Uses thread-local-storage and removes the mutex. Can improve performance in multi-threaded environment, but does use extra memory.
115
88
116
-
For QuickAssist v1.7 the newer usdm memory driver is used directly.
89
+
For QuickAssist v1.7 or later the newer usdm memory driver is used directly.
0 commit comments