From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 106] running dpdk-procinfo or any secondary leading to system memory exhaustion
Date: Mon, 12 Nov 2018 10:44:59 +0000 [thread overview]
Message-ID: <bug-106-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=106
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 memory
exhaustion
Environment: Host & Virtual Machine
Primary App: DPDK l2fwd
Secondary App: simplified custom app
File:
Secondary:
int
main(int argc, char **argv)
{
int ret;
int i;
char c_flag[] = "-c1";
char n_flag[] = "-n4";
char mp_flag[] = "--proc-type=secondary";
char *argp[argc + 3];
uint16_t nb_ports;
argp[0] = argv[0];
argp[1] = c_flag;
argp[2] = n_flag;
argp[3] = mp_flag;
for (i = 1; i < argc; i++)
argp[i + 3] = argv[i];
argc += 3;
ret = rte_eal_init(argc, argp);
if (ret < 0) {
ret = rte_eal_cleanup();
if (ret)
printf("Error from rte_eal_cleanup(), %d\n", ret);
rte_panic("Cannot init EAL\n");
}
ret = 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=$?
while [ $ret -eq 0 ]
do
sync; echo 3 > /proc/sys/vm/drop_caches
./build/app/test
ret=$?
echo "ret ---------------- $ret"
done
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-11-12 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 10:44 bugzilla [this message]
2018-11-12 19:31 ` [Bug 106] running dpdk-procinfo or any secondary leading to system memory exhaustion Mattias Rönnblom
2018-11-13 17:03 ` bugzilla
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-106-3@http.bugs.dpdk.org/ \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.