bz2078943 updated workload partitioning procedure

updated steps

vale linter correction

peer review feedback

Author: sheriff-rh

modules/sno-du-enabling-workload-partitioning.adoc

@@ -48,3 +48,33 @@ spec:
         user:
           name: root
 ----
+
+* The contents of `/etc/crio/crio.conf.d/01-workload-partitioning` should look like this:
++
+[source,text]
+----
+[crio.runtime.workloads.management]
+activation_annotation = "target.workload.openshift.io/management"
+annotation_prefix = "resources.workload.openshift.io"
+resources = { "cpushares" = 0, "cpuset" = "0-1,52-53" } <1>
+----
+<1> The `cpuset` value will vary based on the installation.
+
+If Hyper-Threading is enabled, specify both threads of each core. The `cpuset` must match the reserved CPU set specified in the performance profile.
+
+
+This content should be base64 encoded and provided in the `01-workload-partitioning-content` in the manifest above.
+
+* The contents of `/etc/kubernetes/openshift-workload-pinning` should look like this:
++
+[source,javascript]
+----
+{
+  "management": {
+    "cpuset": "0-1,52-53" <1>
+  }
+}
+----
+<1> The `cpuset` must match the value in `/etc/crio/crio.conf.d/01-workload-partitioning`.
+
+This content should be base64 encoded and provided in the `openshift-workload-pinning-content` in the preceding manifest.