DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 53] rte abort issue on FreeBSD
Date: Mon, 28 May 2018 15:25:21 +0000	[thread overview]
Message-ID: <bug-53-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=53

            Bug ID: 53
           Summary: rte abort issue on FreeBSD
           Product: DPDK
           Version: 18.05
          Hardware: All
                OS: FreeBSD
            Status: CONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: reshma.pattan@intel.com
  Target Milestone: ---

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-05-28 15:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-53-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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).