DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 258] Tap driver unnecessarily triggers timeout on failure
Date: Thu, 25 Apr 2019 15:32:50 +0000	[thread overview]
Message-ID: <bug-258-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190425153250.Dhm0nyE09H5NJ124g2o_NCx9_AT_jL8qqJ3yV5BVgd8@z> (raw)

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.

             reply	other threads:[~2019-04-25 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 15:32 bugzilla [this message]
2019-04-25 15:32 ` bugzilla

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-258-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 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).