Description of problem: Currently, our DPDK checkup VM as well as our reference DPDK-VM spec does not prescribe setting spec.domain.cpu.isolateEmulatorThread=true. Running simple testpmd tests with no disk I/O you will not catch emulator threads or IOthreads isolation issues. However, real applications typically have a couple of threads that do regular I/O (e.g. writing logs to disk). We should enable this attribute. Version-Release number of selected component (if applicable): 4.13 rc How reproducible: Was not reproduced Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Deferring to 4.13.2 to save capacity verifying urgent 4.13.1 bugs.
Copying comment from the linked Jira https://issues.redhat.com/browse/CNV-27911: > Isolation of the emulator thread should not affect zero packet loss (IOW DPDK performance), therefore can't see why this is necessary. > > It should be up to the user to enable this feature (or not), but DPDK zero packet loss should work whether isolation of emulator thread is enabled or disabled.