DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [Bug 84] Primary process broadcasts vdevs during each secondary's vdev scan
@ 2018-08-17 21:27 bugzilla
  0 siblings, 0 replies; only message in thread
From: bugzilla @ 2018-08-17 21:27 UTC (permalink / raw)
  To: dev

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

            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, <vdev name>". 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 secondary.

*Introduced in commit cdb068f031c6 ("bus/vdev: scan by multi-process channel").

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2018-08-17 21:27 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-17 21:27 [dpdk-dev] [Bug 84] Primary process broadcasts vdevs during each secondary's vdev scan bugzilla

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).