From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id B2522F72; Fri, 17 Aug 2018 23:27:48 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Fri, 17 Aug 2018 21:27:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: gage.eads@intel.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 84] Primary process broadcasts vdevs during each secondary's vdev scan 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: , X-List-Received-Date: Fri, 17 Aug 2018 21:27:48 -0000 https://bugs.dpdk.org/show_bug.cgi?id=3D84 Bug ID: 84 Summary: Primary process broadcasts vdevs during each secondary's vdev scan Product: DPDK Version: unspecified Hardware: All OS: All Status: CONFIRMED Severity: minor Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: gage.eads@intel.com Target Milestone: --- A secondary process running vdev_scan() (drivers/bus/vdev/vdev.c) requests = the primary to send the vdevs that the primary was given in its EAL args*. The primary process then receives this request and calls rte_mp_sendmsg() (once= per vdev) to send the vdev information back to the secondary process. The problem is that rte_mp_sendmsg() broadcasts this information to all secondaries, so any existing secondary processes will attempt to re-insert = the vdev with insert_vdev(), fail, then report the error message "failed to add vdev, ". This is harmless, as far as I can tell, but the message makes its seem as though a serious error has occurred. Ideally the primary would send a unicast message to the requesting secondar= y. *Introduced in commit cdb068f031c6 ("bus/vdev: scan by multi-process channe= l"). --=20 You are receiving this mail because: You are the assignee for the bug.=