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 271FF43CBA; Fri, 15 Mar 2024 14:09:32 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 869E642ED0; Fri, 15 Mar 2024 14:09:31 +0100 (CET) Received: from wfout6-smtp.messagingengine.com (wfout6-smtp.messagingengine.com [64.147.123.149]) by mails.dpdk.org (Postfix) with ESMTP id 8937942E6B for ; Fri, 15 Mar 2024 14:09:30 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.west.internal (Postfix) with ESMTP id 8F4D11C000B3; Fri, 15 Mar 2024 09:09:28 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 15 Mar 2024 09:09:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1710508168; x=1710594568; bh=GOVvgkupp5XaJMyOjw+/uLx8+en97aazzlBHivmnJfI=; b= tBOeNrwZ8RceWZ5O8YyAquZPv6UMoY0JK3i4YCvvDEbC51jMLmX9nT+gGF5wEmab jHnOIYTuQl8yUrUE3ugBmE7Ier9atGdP+HQqCME8zxuB9mxPN/LxjBtD1076CAc8 VkeJs8nkBoaojeSnOS+3iO+cFBDkTsZWP7TooNwEspUxr3ii+tR2gYwmnTDIjfhO cTihkTJL0gFdhtUen9jTLNtkdsMhN/ehY19q+Ac1RcUsw9SCxMR8++Q+s/fFxY1X eGoBJ3E6iqAZg0FOxjZWzIzYuzniFho8TRh1tNFgpR+uTrv0SwcmQu/wnvIBkIx1 V8PElFNQY5hTFqetgkNZMg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1710508168; x= 1710594568; bh=GOVvgkupp5XaJMyOjw+/uLx8+en97aazzlBHivmnJfI=; b=N 5S7k4wtRcQRmYOomE9m1fthJ6pJycXZxF1nsVbUkn8Gv0j4qVu4P5d9aVMWy9K5Z cPHIGeJpjE/NE4OvwEPWEGGlIy1SjQ7x5NK444GHEELKBio5yL75Z/wX74KACDht HSNZDR94QoB5tsiAAY7ztekq+nL7DTNmINrWWqIdwKx/y1T1ryspt+87rBYDsw8C Njt42yg6i0HqAragRwfHBvTnQB+DmlG0hSwGbX44njL/BW9od34iQnSXQ9JCczpc 5sPeSVUIvfAmaRhbE5h/Cn6F5S58i0nyu72tmJdHgwuIl/XBqxQB84SKJ/dnwceN leNLdWSe/uyQ5leDqvM/w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjeelgdegkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttdejnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepjeduveehieevuddutdevfffgtdegkeeuveejffejgedtgeegkefg vdeugfefkeejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 15 Mar 2024 09:09:25 -0400 (EDT) From: Thomas Monjalon To: fengchengwen , Gowrishankar Muthukrishnan Cc: dev@dpdk.org, Anoob Joseph , Cheng Jiang , Kevin Laatz , Bruce Richardson , Pavan Nikhilesh Bhagavatula , Amit Prakash Shukla , Jerin Jacob Subject: Re: [EXTERNAL] Re: [v11 0/4] PCI Dev and SG copy support Date: Fri, 15 Mar 2024 14:09:23 +0100 Message-ID: <1994240.8hb0ThOEGa@thomas> In-Reply-To: References: <20240227183555.3932711-1-amitprakashs@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 13/03/2024 09:22, Gowrishankar Muthukrishnan: > Hi Fengchengwen > > > Hi Gowrishankar, > > > > On 2024/3/12 20:24, Gowrishankar Muthukrishnan wrote: > > > Hi Fengchengwen > > > > > >> > > >> Hi Thomas, > > >> > > >> On 2024/3/12 17:15, Thomas Monjalon wrote: > > >>> 07/03/2024 14:55, Gowrishankar Muthukrishnan: > > >>>> Hi Fengchengwen, > > >>>> > > >>>>>> Waiting for a confirmation that this series is good to go. > > >>>>> > > >>>>> In the discuss of thread [1], I hope this patchset continue take a > > >>>>> step forward (means new version) to support bi-direction test just > > >>>>> by > > >> modify config.ini file. > > >>>>> > > >>>> > > >>>> This patch set already exposes all configuration via config.ini. I > > >>>> didn't follow > > >> what is missing. For bi-direction, we can better continue discussing > > >> on that patch. > > >>> > > >>> Chengwen, please can you confirm whether you require a new version? > > >>> Which change exactly is missing? > > >> > > >> This patchset is OK with one sub-test only tackle one DMA direction. > > >> > > > Thanks for the confirmation. > > > > > >> But there is a later patch [1] which will support multiple DMA > > >> directions within one sub-test. > > >> it will add a entry "xfer_mode", but I think it complicate the test, > > >> I prefer we do more in this patchset to support some like > > >> bi-direction just by modify config.ini, some like this: > > >> > > > I think we should discuss about that in bi-directional patch series. This series > > is self-contained and there is no need to add bi-directional as part of this > > series. As far as this patch set is concerned, all the options are exposed via > > config.ini. Can you comment if there is anything missing, assuming that we are > > taking bi-directional support as a separate feature addition. > > > > I have identified some improvements to the dma-perf app, and I plan to do it > > It is unclear at this point what is the issue that you have with the app or this patch set. This series was first submitted on Aug 10 2023. You had acked v8 on Jan 25 2024. After the patches were acked, there were still review comments on variable renames etc, which were all addressed. The patches had been under review for more than 8 months with very slow progress. > > > in 24.07, so if you don't mind, I will incorporate your commits (keeping your > > signed-off-by) and modify to the one that I described above, and then send to > > community (also with my improvements commits). > > I would like to have this series merged first and not pulled into another series. We do have few other features that we would like to add on top. I would assume that you can also add your changes on top. To make contribution easier, isn't it better to accept at least this patch set (as you acked earlier) and then you can continue working on the improvements? OK, one feature at a time. Let's work on top of this patchset applied.