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 99B50A0C47; Thu, 2 Sep 2021 13:43:53 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 18F0F4003E; Thu, 2 Sep 2021 13:43:53 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id 465874003C for ; Thu, 2 Sep 2021 13:43:52 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10094"; a="219092335" X-IronPort-AV: E=Sophos;i="5.84,372,1620716400"; d="scan'208";a="219092335" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Sep 2021 04:43:51 -0700 X-IronPort-AV: E=Sophos;i="5.84,372,1620716400"; d="scan'208";a="691351212" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.1.171]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 02 Sep 2021 04:43:49 -0700 Date: Thu, 2 Sep 2021 12:43:45 +0100 From: Bruce Richardson To: Jerin Jacob Cc: dpdk-dev , "Walsh, Conor" , "Laatz, Kevin" , fengchengwen , Jerin Jacob , Satananda Burla Message-ID: References: <20210826183301.333442-1-bruce.richardson@intel.com> <20210901163216.120087-1-bruce.richardson@intel.com> <20210901163216.120087-4-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] [PATCH v2 3/6] app/test: add basic dmadev copy tests X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Sep 02, 2021 at 04:24:18PM +0530, Jerin Jacob wrote: > > I think 25us will not be enough, e.s.p If is PCI-Dev to PCI-Dev kind > of test cases. > Since it is the functional test case, I think, we can keep it a very > higher range to > support all cases. Maybe 50ms is a good target. > Sure, no problem to push it up. If it turns out that all upstreamed drivers implement the "idle" function we can remove the fallback option completely, but I'll keep it for now and push timeout up. Do you really think it needs to be in the (tens of )millisecond range? Even for tests going across PCI would most transactions not complete in the microsecond range, e.g. 100 usec?