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 4E3B0A057B; Thu, 2 Apr 2020 15:00:37 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9E9D01B91B; Thu, 2 Apr 2020 15:00:36 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 4DF67375B for ; Thu, 2 Apr 2020 15:00:35 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 74B115C01F0; Thu, 2 Apr 2020 09:00:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 02 Apr 2020 09:00:33 -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=mesmtp; bh=tHIEJAra5i0D5Q50hT0aXWAyE+k15jLFjuE+zHaTSI0=; b=HhGvFyjl2KEQ oNZXNiOULXawDrG4gFHb48JMJcwEHw3RT1IZbqm7cS72MSNeHxL0973mZXvST+zn WyO8clrvfoipQqN15hjldHwdkKrldOVIKBYMjB6XD4JwxgcdA7r78Gy/WCALjIFQ yExll3vp32Hfo3Zeogdg4xBbzfb7wXk= 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=fm2; bh=tHIEJAra5i0D5Q50hT0aXWAyE+k15jLFjuE+zHaTS I0=; b=1wcELdC3iTKWdc4thHMYdbwTTpV7v2+pacbJnDydpAHF1jscXl/H/n/12 j8k+WBl3Ca1duiAzibSXRw2zbjMm3spW4avGmaXskN1gGIlYvllOKQRrZ2v0aM8g Tr3ALgvrSs+ZnRj7YNZaqYdyQDATwNWE4vI5dZFSyNLjj8SzynlCLXjoEORmB7T6 UB6X8eYeTRrqt73UiLQEASw30TFPYklqOssvVh5RBZMLxYQSyANyKvN3W9f31+2o ydXec0t3F0sRIMtdoCfcB6U7Xit0PJfKP4jLANAJIZXC7x2b9OGp2j9M5wf9+2kx ZqjhLr2eZzT1PLlgEy4w3/5uICJDw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrtdeggdehfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrsh esmhhonhhjrghlohhnrdhnvght 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 8DA0F3280067; Thu, 2 Apr 2020 09:00:32 -0400 (EDT) From: Thomas Monjalon To: "O'loingsigh, Mairtin" Cc: "dev@dpdk.org" Date: Thu, 02 Apr 2020 15:00:30 +0200 Message-ID: <2019620.dkkaz22YKf@xps> In-Reply-To: References: <1584386504-17800-1-git-send-email-mairtin.oloingsigh@intel.com> <1967048.aiPYRZItUj@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] raw/common: introduce the Multi-function API 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" Hi, 02/04/2020 11:46, O'loingsigh, Mairtin: > From: Thomas Monjalon > > 16/03/2020 20:21, Mairtin o Loingsigh: > > > Multi-function API allows user to chain xforms of various types > > > together in a single operation > > > > Please could you elaborate a bit more? > > Which problem are you trying to address? > > What is the design? > > How it can be used? > > > > For such feature proposal, I recommend a design discussion before starting > > the development. > > The purpose of the Multi-function API is to enable a broader set of > transforms that aren't compression /crypto specific (CRC for example) > We had quite a few discussions on Multi-function in the mails below > > http://mails.dpdk.org/archives/dev/2020-February/157045.html > http://mails.dpdk.org/archives/dev/2020-March/159189.html OK Personally I did not have time yet to dive into this design. But as a first impression, I feel it is not the right API. DPDK is based on classes: ethdev, crypto, compress, baseband, regex I want to understand why your features cannot fit in a class. > The v2 patchset will be ready for this in the coming days > and we will include a cover-letter describing the feature > and referencing back to the RFC discussion this time around I feel we will need a lot of time to discuss the design. If you don't see any consensus on the design in the mailing list, you should request an opinion from the Technical Board. This feature is not a priority for 20.05 release. By the way, it has not been announced in any roadmap.