https://bugs.dpdk.org/show_bug.cgi?id=808
Bug ID: 808
Summary: Unexpected error log 'EAL: Cannot find action:
mp_malloc_response'
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Our test env has two CPU sockets (2 NUMA nodes), and we hope that dpdk can
automatically identify CPU sockets and allocate hugepage memory according to
runtime requirement of application without manual designation, therefore we set
"--socket-mem 0,0 --socket-limit 0,0" into dpdk initialization parameter list.
We do a recovery test case as below for our dpdk application in k8s container:
Test Step:
1. run 'kill -9' to terminate a dpdk primary process
2. restart dpdk primary process
3. run a dpdk secondary process after dpdk primary process restarted
successfully.
Repeat the upper 1-3 test steps for 3 rounds
Expected result:
- no error log was found.
Test result:
- An error log "EAL: Cannot find action: mp_malloc_response" was printed out by
dpdk secondary process after the 3th round test. （The error was NOT found in
the first two rounds test)
Could you help to check this issue ?
Note：
We don't know whether "- socket MEM 0,0 -- socket limit 0,0" is correct.
If not, could you give some suggestions?
--
You are receiving this mail because:
You are the assignee for the bug.
