From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bugzilla@dpdk.org>
Received: by dpdk.org (Postfix, from userid 33)
 id E380529AC; Mon, 12 Nov 2018 11:44:59 +0100 (CET)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Mon, 12 Nov 2018 10:44:59 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: core
X-Bugzilla-Version: 18.05
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: vipin.varghese@intel.com
X-Bugzilla-Status: CONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-106-3@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-dev] [Bug 106] running dpdk-procinfo or any secondary leading
 to system memory exhaustion
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2018 10:45:00 -0000

https://bugs.dpdk.org/show_bug.cgi?id=3D106

            Bug ID: 106
           Summary: running dpdk-procinfo or any secondary leading to
                    system memory exhaustion
           Product: DPDK
           Version: 18.05
          Hardware: x86
                OS: Linux
            Status: CONFIRMED
          Severity: critical
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: vipin.varghese@intel.com
  Target Milestone: ---

Issue: Running dpdk secondary instance in multiple iterations leads to memo=
ry
exhaustion

Environment: Host & Virtual Machine

Primary App: DPDK l2fwd=20

Secondary App: simplified custom app

File:

Secondary:
int
main(int argc, char **argv)
{
        int ret;
        int i;
        char c_flag[] =3D "-c1";
        char n_flag[] =3D "-n4";
        char mp_flag[] =3D "--proc-type=3Dsecondary";
        char *argp[argc + 3];
        uint16_t nb_ports;

        argp[0] =3D argv[0];
        argp[1] =3D c_flag;
        argp[2] =3D n_flag;
        argp[3] =3D mp_flag;

        for (i =3D 1; i < argc; i++)
                argp[i + 3] =3D argv[i];

        argc +=3D 3;

        ret =3D rte_eal_init(argc, argp);
        if (ret < 0) {
                ret =3D rte_eal_cleanup();
                if (ret)
                        printf("Error from rte_eal_cleanup(), %d\n", ret);

                rte_panic("Cannot init EAL\n");
  }

        ret =3D rte_eal_cleanup();
        if (ret)
                printf("Error from rte_eal_cleanup(), %d\n", ret);

        fflush(stdout);
        fflush(stderr);
        return 0;
}

Run script:
#!/bin/sh

./build/app/test
ret=3D$?

while [ $ret -eq 0 ]
do
   sync; echo 3 > /proc/sys/vm/drop_caches
   ./build/app/test
   ret=3D$?
   echo "ret ---------------- $ret"
done

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