From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A04D8A054A; Fri, 19 Feb 2021 07:58:07 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6DB0640395; Fri, 19 Feb 2021 07:58:07 +0100 (CET) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id A91F240042 for ; Fri, 19 Feb 2021 07:58:05 +0100 (CET) IronPort-SDR: yxBDK+PjQIgYzB48swwL4Mj2BDz48tD7heTNmuvGCNxhPo05pKBvHnixMsVo0VqSpEDzMoF/Es E/xzmtPh7Wcw== X-IronPort-AV: E=McAfee;i="6000,8403,9899"; a="181201584" X-IronPort-AV: E=Sophos;i="5.81,189,1610438400"; d="scan'208";a="181201584" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Feb 2021 22:58:04 -0800 IronPort-SDR: zjc6DS9VnfqdGzJL8owrDxWISHQIuOXQPYc2RFxSYvlukvDowMf4gY8g3Oi39/RquezaWugJaf zF1YX0Od2HKQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,189,1610438400"; d="scan'208";a="400885648" Received: from fmsmsx605.amr.corp.intel.com ([10.18.126.85]) by orsmga008.jf.intel.com with ESMTP; 18 Feb 2021 22:58:04 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by fmsmsx605.amr.corp.intel.com (10.18.126.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 18 Feb 2021 22:58:03 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX601.ccr.corp.intel.com (10.109.6.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 19 Feb 2021 14:58:01 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.2106.002; Fri, 19 Feb 2021 14:58:01 +0800 From: "Tu, Lijuan" To: "ohilyard@iol.unh.edu" , "dts@dpdk.org" Thread-Topic: [PATCH] bugfix: Fixed a timeout with mlx5_core on ARM Thread-Index: AQHXAL8UG908ETqSD0ut4suxgTtuzapfF4sQ Date: Fri, 19 Feb 2021 06:58:01 +0000 Message-ID: References: <20210211214415.1454192-1-ohilyard@iol.unh.edu> In-Reply-To: <20210211214415.1454192-1-ohilyard@iol.unh.edu> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH] bugfix: Fixed a timeout with mlx5_core on ARM X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" > The time to unbind this driver has been increasing with DPDK releases, to= the > point that it is now about 14 seconds. This means that, with the default = timeout > of 15 seconds, there isn't much room for any kind of disruption during te= sting. > DTS throwing a timeout error here is not indicative of an acutal problem,= and as > such I have increased the timeout to allow continued stable functioning. = The > new 30 second timeout should have minimal affect on the detection speed o= f > any real error. >=20 > Signed-off-by: Owen Hilyard Applied, thanks