From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 85BFEA0543; Wed, 15 Jul 2020 22:06:59 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DED772C58; Wed, 15 Jul 2020 22:06:57 +0200 (CEST) Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) by dpdk.org (Postfix) with ESMTP id EEF8A2C2B; Wed, 15 Jul 2020 22:06:55 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailnew.nyi.internal (Postfix) with ESMTP id 27BCB583487; Wed, 15 Jul 2020 16:06:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 15 Jul 2020 16:06:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= m0bcQz/nYd9xpXjHeFVVrEFujTWTwwK4yp+KaNpC0iA=; b=mzd0kAJDGNcxAMi3 FLB9YHQggDXBCTifwBQJyWmGlLu+qzHb5j5YCO2/9a7j6fxxiOkLisKfVdpPi4BD EJcCWJVJmpJIC8gMyov/WgNd7iV/OBpWW54XlzEPUWidUvbZezuwZFQC3ZrqyoLM riii2CmndSxffcmn8h5DalHLyD+T67hK/0v6tV7/ShamitNJ06+up4woBRIE5r6J 1xTf7Gq6BUKUaQHwqQn+pTGLsfoo/ADxawrnxvAAd7RZwvz+OMhWTNz8VmNuV4GV FU3a50XglrKFVwry+/ASN+z6Z/7i3bvHt9MecoXlMrC09BwG7A+GqNSEZXcrXdEb d9cllQ== 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=m0bcQz/nYd9xpXjHeFVVrEFujTWTwwK4yp+KaNpC0 iA=; b=AyuXQMQOuf3Gu/9+ARnUrrOdjT7wP2kqAaQWas+V2esdYy0jYls0uKNN8 1fgLaYeO/A4fBnx+ryFZ2tMTVuaCG8YTaL91Yu7LqD3oJKfmdREkawcDVOn2Veba u6Ga5YUUsYsw855jQSgdKPNKY8g2a85HEWsWtpqPsRWRBpmMOHtrbRqr9fu6miVk Se5+3PteRBM7jRBvXTVIrgBrbBrXn8gupoKDRurgWeTATU3C1vHf2n1UC0XlMIPM LfUGVzbha00HyUVJwxutbsuIM9wr1u1tEa81wrMuSr3OZEUvszUWFbtitWR442KY 7ltFYME1gOp4yyqI2BaruG0n/XCRw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfedvgdduheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id CB6BC3060067; Wed, 15 Jul 2020 16:06:52 -0400 (EDT) From: Thomas Monjalon To: Arek Kusztal , Akhil Goyal Cc: "dev@dpdk.org" , "fiona.trahe@intel.com" , "techboard@dpdk.org" , Anoob Joseph , "Somalapuram, Amaranath" , Ankur Dwivedi , "ruifeng.wang@arm.com" , "De Lara Guarch, Pablo" , Nagadheeraj Rottela Date: Wed, 15 Jul 2020 22:06:51 +0200 Message-ID: <6538553.9OgRhud1Dp@thomas> In-Reply-To: References: <20200715155043.12476-1-arkadiuszx.kusztal@intel.com> <2505982.uU9X1ItemK@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/5] app: add multi process crypto application X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" 15/07/2020 21:25, Akhil Goyal: > Hi Thomas, > > > > 15/07/2020 20:26, Akhil Goyal: > > > Hi Arek, > > > > > > > > Due to increasing interest in multi process support for crypto PMDs > > > > new test app can be added so in overview we can say that: > > > > > > > > The Multi-process Crypto application is a simple application that > > > > allows to run crypto related operations in a multiple process environment. It > > > > builds on the EAL primary/secondary process infrastructure. > > > > > > > > v3: > > > > - split into multiple patches > > > > - refactored parts of code > > > > > > Looking at the comments on this patchset, I believe the app may not > > > be ready by RC2 which falls at end of this week for crypto tree. > > > I have not started review of the application yet. > > > I see it getting deferred for the next release if it is not added in RC3. > > > > In general applications are approved by the technical board. > > This app was not discussed at all. > > And I think it will be rejected, > > because I don't see the value of adding a test application just for > > multi-process usage. > > > Is this a recent change that a new application need to be discussed in techboard > first? I see that test-sad was added without discussion in the techboard. We started having such discussion this year (maybe a bit earlier), because there are too many applications, and some examples were removed. > I see this application as a useful tool to test the readiness of a driver to be used > in a multi process environment. If app is not a correct place to host it, should it be > added in examples/multi_process/. I also suggested that in v2 but it makes more > sense in app as it is a unit test application which does not have any relevance as > standalone application as crypto may not be used standalone without ethernet > for multi process scenario. > My first preference was to modify l2fwd-crypto to be used as a multi process proof > Application but it also make sense to have a unit test application to verify standalone > crypto PMDs. > Open for comments from other crypto PMD owners. I agree it looks like unit tests. Can it be added to app/test/test_cryptodev* ?