[dpdk-dev,v2] doc: add known issue of rte abort on FreeBSD
Checks
Commit Message
Added known issue of rte_abort taking a long time
on FreeBSD due to recent memory subsystem rework.
Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
v2: reworded.
---
doc/guides/rel_notes/release_18_05.rst | 15 +++++++++++++++
1 file changed, 15 insertions(+)
Comments
> Added known issue of rte_abort taking a long time on FreeBSD due to recent
> memory subsystem rework.
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> v2: reworded.
> ---
> doc/guides/rel_notes/release_18_05.rst | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
<...>
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
> -----Original Message-----
> From: Pattan, Reshma
> Sent: Monday, May 21, 2018 11:16 AM
> To: dev@dpdk.org
> Cc: Burakov, Anatoly <anatoly.burakov@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Pattan, Reshma <reshma.pattan@intel.com>
> Subject: [PATCH v2] doc: add known issue of rte abort on FreeBSD
>
> Added known issue of rte_abort taking a long time on FreeBSD due to recent
> memory subsystem rework.
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Could you open an Bugzilla defect for this and add it to the text.
Like this patch: http://dpdk.org/dev/patchwork/patch/40475/
Thanks,
John
@@ -485,6 +485,21 @@ Known Issues
dpdk-pdump example and any other applications using librte_pdump, cannot work
with older version DPDK primary applications.
+* **rte_abort takes a long time on FreeBSD.**
+
+ DPDK processes now allocates a large area of virtual memory address space,
+ with this change during rte_abort FreeBSD now dumps the contents of the
+ whole reserved memory range, not just the used portion, to a core dump file.
+ Write this large core file can take a significant amount of time, causing
+ processes to appear hung on the system.
+
+ The work around for the issue is to set the system resource limits for core
+ dumps before running any tests e.g."limit coredumpsize 0". This will
+ effectively disable core dumps on FreeBSD. If they are not to be completely
+ disabled, a suitable limit, e.g. 1G might be specified instead of 0. This
+ needs to be run per-shell session, or before every test run. This change
+ can also be made persistent by adding "kern.coredump=0" to /etc/sysctl.conf
+
Shared Library Versions
-----------------------