On Linux (and probably BSD), CPU 0 can not be fully isolated because it receives timer interrupts and is used for other kernel related functions. The DPDK documentation should be updated to tell users to avoid polling on that CPU.
Signed-off-by: Stephen Hemminger <step...@networkplumber.org> --- doc/guides/linux_gsg/enable_func.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/guides/linux_gsg/enable_func.rst b/doc/guides/linux_gsg/enable_func.rst index 5511640cb8..dc33ffc718 100644 --- a/doc/guides/linux_gsg/enable_func.rst +++ b/doc/guides/linux_gsg/enable_func.rst @@ -131,9 +131,14 @@ from running on those cores, it is possible to use the Linux kernel parameters ``isolcpus``, ``nohz_full``, ``irqaffinity`` to isolate them from the general Linux scheduler tasks. +.. note:: + + It is not recommended to use CPU core 0 for DPDK polling applications + because it can not be isolated from other system and kernel activity. + For example, if a given CPU has 0-7 cores -and DPDK applications are to run on logical cores 2, 4 and 6, -the following should be added to the kernel parameter list: +and DPDK applications are to run on logical cores 2, 4 and 6. +The following should be added to the kernel parameter list: .. code-block:: console -- 2.43.0
