[Bug 1071] Deadlock on memory allocation (rte_memzone_reserve_aligned)

[Bug 1071] Deadlock on memory allocation (rte_memzone_reserve_aligned)

[bugzilla]

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

            Bug ID: 1071
           Summary: Deadlock on memory allocation
                    (rte_memzone_reserve_aligned)
           Product: DPDK
           Version: 21.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: a.dibacco.ks@gmail.com
  Target Milestone: ---

Created attachment 218
  --> https://bugs.dpdk.org/attachment.cgi?id=218&action=edit
simple_mem_mp program

I launch the attached program on a 56c, 2 numa x86 machine:

The primary (named simple_mem_mp) does the following:

1) Starts a secondary (same image but named simple_mem_mp_sec)
2) Allocates a huge number (512) of 2M pages and release them
3) Starts a few eal threads that also allocate/release other 2M pages forever
4) Waits for the secondary to exit
5) Go to bullet 1


The secondary (same image as primary but named simple_mem_mp_sec):

1) Starts a few eal threads that allocate 100x2M pages and then exit
2) Wait for threads to finish and then exit

The secondary is alive for almost 4 secs before exiting.

After a few iterations a deadlock is experienced. The secondary seems to start
but cannot complete the rte_eal_init and I see that lslocks reports this (a
flock cannot get the lock on /dev/hugepages2M):

simple_mem_mp   171272 FLOCK      WRITE* 0     0          0 /dev/hugepages2M...
simple_mem_mp   171272 FLOCK      WRITE  0     0          0 /dev/hugepages2M...

Here is a log:

Starting core on secondary 14
Starting core on secondary 15
Starting core on secondary 7
Starting core on secondary 8
Starting core on secondary 9
Secondary started
Proc type 1 exiting


EAL: Detected CPU lcores: 56
EAL: Detected NUMA nodes: 2
EAL: Auto-detected process type: SECONDARY
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_171319_224be24c4ae
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
Starting core on secondary 6
Starting core on secondary 7
Starting core on secondary 8
Starting core on secondary 9
Starting core on secondary 10
Starting core on secondary 11
Secondary started
Starting core on secondary 12
Starting core on secondary 14
Starting core on secondary 15
Starting core on secondary 13
Proc type 1 exiting

EAL: Detected CPU lcores: 56
EAL: Detected NUMA nodes: 2
EAL: Auto-detected process type: SECONDARY
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_171333_22b0fbb7ab4
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized

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

[Bug 1071] Deadlock on memory allocation (rte_memzone_reserve_aligned)

[bugzilla]

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

Anatoly Burakov (anatoly.burakov@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #9 from Anatoly Burakov (anatoly.burakov@intel.com) ---
It sounds like a good idea, but I don't think this is something a lot of people
have to deal with to be honest, because this isn't a normal use case. If you
were to be willing to submit a patch, I'd gladly review it.

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