DPDK patches and discussions
 help / color / mirror / Atom feed
From: Reshma Pattan <reshma.pattan@intel.com>
To: dev@dpdk.org
Cc: anatoly.burakov@intel.com, john.mcnamara@intel.com,
	Reshma Pattan <reshma.pattan@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: add known issue of rte abort on FreeBSD
Date: Mon, 21 May 2018 11:16:16 +0100	[thread overview]
Message-ID: <1526897776-23859-1-git-send-email-reshma.pattan@intel.com> (raw)
In-Reply-To: <1526653438-13256-1-git-send-email-reshma.pattan@intel.com>

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(+)

diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
index 3dcb62538..65014a284 100644
--- a/doc/guides/rel_notes/release_18_05.rst
+++ b/doc/guides/rel_notes/release_18_05.rst
@@ -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
 -----------------------
-- 
2.14.3

  parent reply	other threads:[~2018-05-21 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 14:23 [dpdk-dev] [PATCH] " Reshma Pattan
2018-05-21  9:28 ` Burakov, Anatoly
2018-05-21 10:16 ` Reshma Pattan [this message]
2018-05-23 15:44   ` [dpdk-dev] [PATCH v2] " Kovacevic, Marko
2018-05-28 15:30   ` Mcnamara, John
2018-05-28 15:40   ` [dpdk-dev] [PATCH v3] " Reshma Pattan
2018-05-28 16:53     ` Mcnamara, John
2018-05-30 12:10       ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1526897776-23859-1-git-send-email-reshma.pattan@intel.com \
    --to=reshma.pattan@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).