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 295ADA0547; Tue, 19 Oct 2021 21:08:44 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9283E40683; Tue, 19 Oct 2021 21:08:43 +0200 (CEST) Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) by mails.dpdk.org (Postfix) with ESMTP id 9129240142 for ; Tue, 19 Oct 2021 21:08:41 +0200 (CEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id D0363580F68; Tue, 19 Oct 2021 15:08:39 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 19 Oct 2021 15:08:39 -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=fm2; bh= Z7co7TiDetqqkLVUdHB8yeyGlTJzI9fIvIQ+Z5FI6lU=; b=q6kvHuYZ1PyoQqh7 wx0sGUzci5uDhwucGN0HtxHJp5UmHxC2aVyz/nsFliqF3ITkvSeElcnOT+h2OM9y MY+AVMit+jgYXzb7kbT122TuInswgVw2+u8/XWnIXNCdQ2fURjo27M7aYqByJ71F MDAk26kvPxY5GA7PzCqqC6BmkPmfXj5yAJU7Md9UX4Q2aSh3IOHBkzEJP2NAIVPy hiLhmAUD3BArlmUHuuNvZEkS1byezz6egguHuddnqdG4C7rCWPoz6u1XsJv19rJz oS4dlJKbnPhdqsU4b7k8t4q0Dcs0pS4cIJPKOV+dq3gl8+K83I4FtywSlBW0kXgh cL7u3w== 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=fm1; bh=Z7co7TiDetqqkLVUdHB8yeyGlTJzI9fIvIQ+Z5FI6 lU=; b=UKfeA0pfUHm51KvUOtyGoQshNW0cW+F3gTcChAU0igDU8Hk0Gys5bc0xM LbOLyDae6Opr5DMEZ2DFqoysMThjmQUKvNXBjQJCeIUqQYEAbANHNOuLA05zfD4E fKP30DIDralVznkxcOe77PNLtOyt3CBges68AU7W+Xg2c8+jR/I1/yJwhjylrvjV xt/p9pP5RYyIvQS8LpSPX4XpbAglcRh3a1VKKGNAcy/TYhPn/sR8mdNMI94GdWZW Lb5zyRT8PjWLsSDup8J3LbwC7ixIOeAH7c3nDKQEe9c/+xwNX8gaPtNDbcwKrqMB TQptVoQDZWfRLhwOft5XQB2rSxopw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddvvddguddujecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtuf ertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepudeggfdvfeduffdtfe eglefghfeukefgfffhueejtdetuedtjeeuieeivdffgeehnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh drnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 19 Oct 2021 15:08:28 -0400 (EDT) From: Thomas Monjalon To: jerinj@marvell.com Cc: dev@dpdk.org, ferruh.yigit@intel.com, ajit.khaparde@broadcom.com, aboyer@pensando.io, andrew.rybchenko@oktetlabs.ru, beilei.xing@intel.com, bruce.richardson@intel.com, chas3@att.com, chenbo.xia@intel.com, ciara.loftus@intel.com, dsinghrawat@marvell.com, ed.czeck@atomicrules.com, evgenys@amazon.com, grive@u256.net, g.singh@nxp.com, zhouguoyang@huawei.com, haiyue.wang@intel.com, hkalra@marvell.com, heinrich.kuhn@corigine.com, hemant.agrawal@nxp.com, hyonkim@cisco.com, igorch@amazon.com, irusskikh@marvell.com, jgrajcia@cisco.com, jasvinder.singh@intel.com, jianwang@trustnetic.com, jiawenwu@trustnetic.com, jingjing.wu@intel.com, johndale@cisco.com, john.miller@atomicrules.com, linville@tuxdriver.com, keith.wiles@intel.com, kirankumark@marvell.com, oulijun@huawei.com, lironh@marvell.com, longli@microsoft.com, mw@semihalf.com, spinler@cesnet.cz, matan@nvidia.com, matt.peters@windriver.com, maxime.coquelin@redhat.com, mk@semihalf.com, humin29@huawei.com, pnalla@marvell.com, ndabilpuram@marvell.com, qiming.yang@intel.com, qi.z.zhang@intel.com, radhac@marvell.com, rahul.lakkireddy@chelsio.com, rmody@marvell.com, rosen.xu@intel.com, sachin.saxena@oss.nxp.com, skoteshwar@marvell.com, shshaikh@marvell.com, shaibran@amazon.com, shepard.siegel@atomicrules.com, asomalap@amd.com, somnath.kotur@broadcom.com, sthemmin@microsoft.com, steven.webster@windriver.com, skori@marvell.com, mtetsuyah@gmail.com, vburru@marvell.com, viacheslavo@nvidia.com, xiao.w.wang@intel.com, cloud.wangxiaoyun@huawei.com, yisen.zhuang@huawei.com, yongwang@vmware.com, xuanziyang2@huawei.com, pkapoor@marvell.com, nadavh@marvell.com, sburla@marvell.com, pathreya@marvell.com, gakhil@marvell.com, mdr@ashroe.eu, dmitry.kozliuk@gmail.com, anatoly.burakov@intel.com, cristian.dumitrescu@intel.com, honnappa.nagarahalli@arm.com, mattias.ronnblom@ericsson.com, ruifeng.wang@arm.com, drc@linux.vnet.ibm.com, konstantin.ananyev@intel.com, olivier.matz@6wind.com, jay.jayatheerthan@intel.com, asekhar@marvell.com, pbhagavatula@marvell.com, eagostini@nvidia.com, david.marchand@redhat.com, tom@herbertland.com Date: Tue, 19 Oct 2021 21:08:27 +0200 Message-ID: <6870595.fqHcUuC4to@thomas> In-Reply-To: <20211019181459.1709976-1-jerinj@marvell.com> References: <20211019181459.1709976-1-jerinj@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [RFC PATCH 0/1] Dataplane Workload Accelerator library 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" 19/10/2021 20:14, jerinj@marvell.com: > Definition of Dataplane Workload Accelerator > -------------------------------------------- > Dataplane Workload Accelerator(DWA) typically contains a set of CPUs, > Network controllers and programmable data acceleration engines for > packet processing, cryptography, regex engines, baseband processing, etc. > This allows DWA to offload compute/packet processing/baseband/ > cryptography-related workload from the host CPU to save the cost and power. > Also to enable scaling the workload by adding DWAs to the Host CPU as needed. > > Unlike other devices in DPDK, the DWA device is not fixed-function > due to the fact that it has CPUs and programmable HW accelerators. > This enables DWA personality/workload to be completely programmable. > Typical examples of DWA offloads are Flow/Session management, > Virtual switch, TLS offload, IPsec offload, l3fwd offload, etc. If I understand well, the idea is to abstract the offload of some stack layers in the hardware. I am not sure we should give an API for such stack layers in DPDK. It looks to be the role of the dataplane application to finely manage how to use the hardware for a specific dataplane. I believe the API for such layer would be either too big, or too limited, or not optimized for specific needs. If we really want to automate or abstract the HW/SW co-design, I think we should better look at compiler work like P4 or PANDA.