From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id 5C4CFA05D3
	for <public@inbox.dpdk.org>; Thu, 25 Apr 2019 17:32:52 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 4DB0D1B5C1;
	Thu, 25 Apr 2019 17:32:51 +0200 (CEST)
Received: by dpdk.org (Postfix, from userid 33)
 id 9D7AC1B5C1; Thu, 25 Apr 2019 17:32:50 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Thu, 25 Apr 2019 15:32:50 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: ethdev
X-Bugzilla-Version: 19.05
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: minor
X-Bugzilla-Who: anatoly.burakov@intel.com
X-Bugzilla-Status: CONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-258-3@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-dev] [Bug 258] Tap driver unnecessarily triggers timeout on
	failure
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
Message-ID: <20190425153250.Dhm0nyE09H5NJ124g2o_NCx9_AT_jL8qqJ3yV5BVgd8@z>

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

            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 h=
as
arrived from the primary, the call was successful. When the primary encount=
ers
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 l=
eads
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.

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