BZ1883782: Removing LatencySensitive reference

BZ1883782: Removing LatencySensitive reference

BZ1883782: Removing LatencySensitive reference

BZ1883782: Removing LatencySensitive reference

BZ1883782: Implemented SME review comments

Implemented peer review comments

Implemented peer review comments

Implemented peer review comments

Author: snarayan-redhat

modules/nw-sriov-topology-manager.adoc

@@ -9,8 +9,14 @@ You can create a NUMA aligned SR-IOV pod by restricting SR-IOV and the CPU resou
 
 .Prerequisites
 
-* Install the OpenShift CLI (`oc`).
-* Enable a LatencySensitive profile and configure the CPU Manager policy to `static`.
+* You have installed the OpenShift CLI (`oc`).
+* You have configured the CPU Manager policy to `static`. For more information on CPU Manager, see the "Additional resources" section.
+* You have configured the Topology Manager policy to `single-numa-node`.
++
+[NOTE]
+====
+When `single-numa-node` is unable to satisfy the request, you can configure the Topology Manager policy to `restricted`.
+====
 
 .Procedure
 

networking/hardware_networks/add-pod.adoc

@@ -18,3 +18,4 @@ include::modules/nw-sriov-topology-manager.adoc[leveloffset=+1]
 
 - xref:../../networking/hardware_networks/configuring-sriov-device.adoc#configuring-sriov-device[Configuring an SR-IOV Ethernet network attachment]
 - xref:../../networking/hardware_networks/configuring-sriov-ib-attach.adoc#configuring-sriov-ib-attach[Configuring an SR-IOV InfiniBand network attachment]
+- xref:../../scalability_and_performance/using-cpu-manager.adoc#using-cpu-manager[Using CPU Manager]