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: device_plugins/deploy_qat.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -60,10 +60,10 @@ Users can use the steps below to customize the QAT resource configuration:
60
60
```
61
61
Options:
62
62
`dc`: Configure all the QAT VF devices managed by the device plugin CR for compression/decompression.
63
-
`sym` or `asym`: Configure all the QAT VF devices managed by the device plugin CR for cryptography
63
+
`sym;asym`: Configure all the QAT VF devices managed by the device plugin CR for cryptography
64
64
2. Create QAT device plugin CR with `-provisioning-config` set as qat-config.
65
65
66
66
# Run Intel QAT based workloads on RHOCP
67
67
To run the Intel QAT based workloads as an unprivileged pod (see [issue](https://github.com/intel/intel-technology-enabling-for-openshift/issues/122)). The customized `qat-scc` Security Context Constraint (SCC) is provided to bind with service account and run the QAT based workload.
68
68
69
-
See [Verify Intel QuickAssist Technology Provisioning](https://github.com/intel/intel-technology-enabling-for-openshift/tree/main/tests/l2#verify-intel-quickassist-technology-provisioning) for the detailed steps.
69
+
See [Verify Intel QuickAssist Technology Provisioning](/tests/l2/README.md#verify-intel®-quickassist-technology-provisioning) for the detailed steps.
0 commit comments