https://bugs.dpdk.org/show_bug.cgi?id=258
Bug ID: 258
Summary: Tap driver unnecessarily triggers timeout on failure
Product: DPDK
Version: 19.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: minor
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: anatoly.bura...@intel.com
Target Milestone: ---
When calling tap_mp_attach_queues(), secondary assumes that if a response has
arrived from the primary, the call was successful. When the primary encounters
an error in tap_mp_sync_queues(), it will simply return -1 without sending a
reply. There is no way for a primary to indicate that it has received a
processed the request, but have encountered an error while doing so. This leads
to a situation where the secondary will timeout on waiting for primary to
respond if the primary has encountered failure.
The correct usage of IPC is for primary to respond with a status code, and for
secondary to check whether the status code matches success or failure.
--
You are receiving this mail because:
You are the assignee for the bug.
