[dpdk-dev] [Bug 73] In a multi-process setup, secondary processes fail to receive any packet

[dpdk-dev] [Bug 73] In a multi-process setup, secondary processes fail to receive any packet

[bugzilla]

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

            Bug ID: 73
           Summary: In a multi-process setup, secondary processes fail to
                    receive any packet
           Product: DPDK
           Version: 18.02
          Hardware: x86
                OS: Linux
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: guillaume.girard@intel.com
  Target Milestone: ---

We have built an application on top of DPDK listening to certain streams of
packets and reporting statistics on those. The application is working with a
specific Ethernet port specified at the command-line.

The application is multi-process aware, so you can start a primary and several
secondaries, all listening to their own ports. This works perfectly fine on a
X550T-based setup with up to 8 ports (driver is xgbe).

However, when moving to an X772T-based setup (driver is i40e), the secondaries
stopped receiving any packets. The primary works as usual, and sees all packets
for its own port. The secondaries get "packets" that consists of 60 to 300
bytes, all zeroes, at a rate of one per second or so.

I tried to run the same setup with multiple primaries separated by their file
prefix, but the same issue happened (which process gets the packets changes
though).

I finally refactored the application to run separate threads in the same
process instead, and that worked fine. All threads see all the packets they
expect.

I suspect that ixgbe and i40e differ in how they handle this, and that might
cause the bug, but obviously, there might be other differences between hosts
that might be causing this as well. Not being familiar with DPDK, I haven't
searched any further, but I'll be happy to do so if somebody can give me a hint
of where to start looking.

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