From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 84] Primary process broadcasts vdevs during each secondary's vdev scan
Date: Fri, 17 Aug 2018 21:27:48 +0000 [thread overview]
Message-ID: <bug-84-3@http.bugs.dpdk.org/> (raw)
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.
reply other threads:[~2018-08-17 21:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-84-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.