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 31873A0C4C; Thu, 2 Sep 2021 16:22:13 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1644340041; Thu, 2 Sep 2021 16:22:13 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mails.dpdk.org (Postfix) with ESMTP id F251B4003C for ; Thu, 2 Sep 2021 16:22:11 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10094"; a="304694193" X-IronPort-AV: E=Sophos;i="5.85,372,1624345200"; d="scan'208";a="304694193" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Sep 2021 07:21:49 -0700 X-IronPort-AV: E=Sophos;i="5.85,372,1624345200"; d="scan'208";a="542752998" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.1.171]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 02 Sep 2021 07:21:47 -0700 Date: Thu, 2 Sep 2021 15:21:44 +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 06:35:07PM +0530, Jerin Jacob wrote: > On Thu, Sep 2, 2021 at 5:13 PM Bruce Richardson > wrote: > > > > 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? > > Based on busload and size of buffers the completion time can vary. I > think, 1 ms could be > good trade-off. Also, In the future some HW needs beyond that then we > can increase. Ok, thanks.