From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 00E5D1B6B7 for <dev@dpdk.org>; Fri, 3 Nov 2017 20:24:24 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7851320BC5; Fri, 3 Nov 2017 15:24:24 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 03 Nov 2017 15:24:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=1wZGiOZWk6M/vSPcrfG+1aPHE/ +2tKtJhbgSh4Tl1v4=; b=C1gdFGp0eDUmgC8BCRtvrQFyc7ob641UwVGR8YXmOy dEGmavzSO0qU38HC+nNkulomeKT16ryD+lzcrK7lpIua856V4fNFY3bUk7SznmPs RDpEqHGYkBHauqfOUDn5OTw35GKwIltRZHUWLb1YIjyjHI5eTU2KxhtRCgjOu0fk 4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=1wZGiO ZWk6M/vSPcrfG+1aPHE/+2tKtJhbgSh4Tl1v4=; b=NM6NmCTZFK9bNJTlM6BoJJ IezmuDcKOWjV2NlHsUsfi0yUNyJyDd5ySvGEF1Mwmeg5nLktTTjBMJEc40EwFRg8 /jdwEXrqixJZbgQkNsMSsu2RNTnBiK8dYHh2YmBqUlYPHsuWS5OElFhQJCyeetqh RPJ+3nMDLy/tfAiMZUK8UU57llKO5U64ilfDx7HL3QG63g1MmwdrataqLDjTyiPg 3d3tR6mRjx1a83jLOjZ5+ihuuTs5WCczuOBEUe3li7JZyT5g2TFFsG+X7UQLO0sM ZRSZ2uGFNK8sx8EOIqAgIpC2umj7IIh8xbaWjqtxoMiTJIw1kae+HQzLnnL20wWg == X-ME-Sender: <xms:aML8Wa3SmSvBLmGBUCoiTi25Yp-FQj4Hro-64aOktbzuVRCaTDQGLQ> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 316187E6B8; Fri, 3 Nov 2017 15:24:24 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: "Mody, Rasesh" <Rasesh.Mody@cavium.com> Cc: Ferruh Yigit <ferruh.yigit@intel.com>, Stephen Hemminger <stephen@networkplumber.org>, "Tan, Jianfeng" <jianfeng.tan@intel.com>, Jingjing Wu <jingjing.wu@intel.com>, "Thotton, Shijith" <Shijith.Thotton@cavium.com>, Gregory Etelson <gregory@weka.io>, "Patil, Harish" <Harish.Patil@cavium.com>, dev@dpdk.org, George Prekas <george.prekas@epfl.ch>, Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Date: Fri, 03 Nov 2017 20:24:22 +0100 Message-ID: <12814007.65nxXEtm0z@xps> In-Reply-To: <CY4PR0701MB382781A0DF18B5100CCD21109F5D0@CY4PR0701MB3827.namprd07.prod.outlook.com> References: <efabcaad-b0e9-e360-22b5-953b0bc20032@intel.com> <506f596c-f7e3-56b1-d13a-17b49bc3945a@intel.com> <CY4PR0701MB382781A0DF18B5100CCD21109F5D0@CY4PR0701MB3827.namprd07.prod.outlook.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] igb_uio: remove device reset in open X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Fri, 03 Nov 2017 19:24:25 -0000 03/11/2017 20:18, Mody, Rasesh: > From: Ferruh Yigit [mailto:ferruh.yigit@intel.com] > > On 11/2/2017 11:45 AM, Mody, Rasesh wrote: > > > From: Ferruh Yigit [mailto:ferruh.yigit@intel.com] > > >> On 11/2/2017 10:34 AM, Mody, Rasesh wrote: > > > We are ok as we have at least some way to disable the reset, please send a > > patch. > > > > Sent http://dpdk.org/dev/patchwork/patch/31143/, can you please test? > > The testing of BNX2X looks OK with this patch. However, the solution has following drawbacks: > - an application will need to be recompiled to have the igb_uio kernel module rebuilt to support bnx2x devices > - this will break pre-compiled solutions that are provided with an OS such as RHOSP or as part of a pre-compiled VNF > > We can live with this temporary solution for now. In the long term, we may have to revisit this. > We are also looking at why bnx2x FLR is taking this long. Yes, I think the long term solution should be to fix your PMD or your firmware. Please keep us posted when you find the root cause with your device. Thanks