anchor.diff:  
   DPDK relies on both performance and SR-IOV features, so the test suite configures both a performance profile and SR-IOV networks, so the impacts are the same as those described in SR-IOV testing and performance testing.
   
  +[id="cnf-performing-end-to-end-tests-container-mount-namespace_{context}"]
  +=== Container-mount-namespace
  +
  +The validation test for `container-mount-namespace` mode only checks that the appropriate `MachineConfig` objects are present and active, and has no additional impact on the node.
  +
   [id="cnf-performing-end-to-end-tests-cleaning-up_{context}"]
   === Cleaning up
   
  
positive.code: * A performance profile having `profile.Spec.CPU.Isolated = 1`.
  * A performance profile having `profile.Spec.RealTimeKernel.Enabled == true`.
  * A node with no huge pages usage.
  
  [id="limiting-nodes-used-during-tests_{context}"]
  === Limiting the nodes used during tests
  
negative.code: * Having the Performance Addon Operator installed
  * Having the SR-IOV Operator installed
  * Having the PTP Operator installed
  * Enabling the `contain-mount-namespace` mode via machine config
  * Using OVN kubernetes as the SDN
  
  Latency tests, a part of the CNF-test container, also require the same validations. For more information about running a latency test, see the Running the latency tests section.
  