From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id AB5C4A05D3 for ; Thu, 23 May 2019 16:23:20 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 507D91B949; Thu, 23 May 2019 16:23:20 +0200 (CEST) Received: by dpdk.org (Postfix, from userid 33) id A17101B949; Thu, 23 May 2019 16:23:18 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Thu, 23 May 2019 14:23:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: other X-Bugzilla-Version: 18.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: oleksandr.gromovskyi@harmonicinc.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: 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 284] Secondary not able to Rx/TX after primary dies in symmetric multiprocess X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D284 Bug ID: 284 Summary: Secondary not able to Rx/TX after primary dies in symmetric multiprocess Product: DPDK Version: 18.11 Hardware: x86 OS: Linux Status: CONFIRMED Severity: major Priority: Normal Component: other Assignee: dev@dpdk.org Reporter: oleksandr.gromovskyi@harmonicinc.com Target Milestone: --- In our project we plan to use symmetric multiprocessing to have redundancy = on application level. So if primary crashes secondary still can process packets from the eth ports. But currently i see that when primary is alive secondary can receive the da= ta from port and everything works as expected, but after primary dies secondary also stop receiving the data. I tested same in symmetric_mp example and problem is same. According to documentation: https://doc.dpdk.org/guides-18.11/sample_app_ug/multi_process.html ... it is not necessary to restart all processes if the primary instance dies. Instead, that process can be restarted as a secondary,=20 ... I'm executing primary and secondary with next two commands ./build/symmetric_mp -c 1 -n 4 --proc-type=3Dauto -- -p 3 --num-procs=3D2 --proc-id=3D0 ./build/symmetric_mp -c 2 -n 4 --proc-type=3Dauto -- -p 3 --num-procs=3D2 --proc-id=3D1 I modified the code to print statistics each second and see rx/tx increasing but only till primary is alive. EAL: Detected 4 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Probing VFIO support... EAL: PCI device 0000:01:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe EAL: PCI device 0000:01:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe # Initialising port 0... # Initialising port 1... Checking link status...done Port0 Link Up. Speed 10000 Mbps - full-duplex Port1 Link Up. Speed 10000 Mbps - full-duplex APP: Finished Process Init. Lcore 0 using ports 0 1 lcore 0 using queue 0 of each port Port 0: RX - 0, TX - 0, Drop - 0 Port 1: RX - 0, TX - 0, Drop - 0 Port 0: RX - 0, TX - 1, Drop - 0 Port 1: RX - 1, TX - 0, Drop - 0 Port 0: RX - 0, TX - 2, Drop - 0 Port 1: RX - 2, TX - 0, Drop - 0 Port 0: RX - 0, TX - 3, Drop - 0 Port 1: RX - 3, TX - 0, Drop - 0 Port 0: RX - 0, TX - 4, Drop - 0 Port 1: RX - 4, TX - 0, Drop - 0 Restarting of primary as secondary ./build/symmetric_mp -c 1 -n 4 --proc-type=3Dsecondary -- -p 3 --num-procs= =3D2 --proc-id=3D0 does not help. Only stop of all applications and starting of primary again makes rx/tx working again. --=20 You are receiving this mail because: You are the assignee for the bug.=