* [dpdk-dev] [Bug 258] Tap driver unnecessarily triggers timeout on failure
@ 2019-04-25 15:32 bugzilla
2019-04-25 15:32 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2019-04-25 15:32 UTC (permalink / raw)
To: dev
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.burakov@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.
^ permalink raw reply [flat|nested] 2+ messages in thread* [dpdk-dev] [Bug 258] Tap driver unnecessarily triggers timeout on failure
2019-04-25 15:32 [dpdk-dev] [Bug 258] Tap driver unnecessarily triggers timeout on failure bugzilla
@ 2019-04-25 15:32 ` bugzilla
0 siblings, 0 replies; 2+ messages in thread
From: bugzilla @ 2019-04-25 15:32 UTC (permalink / raw)
To: dev
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.burakov@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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-04-25 15:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-25 15:32 [dpdk-dev] [Bug 258] Tap driver unnecessarily triggers timeout on failure bugzilla
2019-04-25 15:32 ` 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).