From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 84] Primary process broadcasts vdevs during each
secondary's vdev scan
Date: Fri, 17 Aug 2018 21:27:48 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path:
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=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.=