From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 2C06EAAEA for ; Fri, 18 May 2018 16:24:02 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2018 07:24:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,415,1520924400"; d="scan'208";a="51967011" Received: from sivswdev02.ir.intel.com (HELO localhost.localdomain) ([10.237.217.46]) by orsmga003.jf.intel.com with ESMTP; 18 May 2018 07:24:00 -0700 From: Reshma Pattan To: dev@dpdk.org Cc: anaotoly.burakov@intel.com, john.mcnamara@intel.com, Reshma Pattan Date: Fri, 18 May 2018 15:23:58 +0100 Message-Id: <1526653438-13256-1-git-send-email-reshma.pattan@intel.com> X-Mailer: git-send-email 1.7.0.7 Subject: [dpdk-dev] [PATCH] doc: add known issue of rte abort on FreeBSD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 14:24:03 -0000 Added known issue of rte_abort taking a long time on FreeBSD due to recent memory subsystem rework. Signed-off-by: Reshma Pattan --- 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..c01781956 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 due to memory subsytsem rework.** + + With the recent memory subsystem changes, DPDK processes now allocate a large + area of virtual memory address space. During rte_abort FreeBSD will dump 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