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 87FA4A034F; Mon, 7 Jun 2021 12:50:11 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 07C9E4067E; Mon, 7 Jun 2021 12:50:11 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id B2D8640147 for ; Mon, 7 Jun 2021 12:50:09 +0200 (CEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 592225C00FB; Mon, 7 Jun 2021 06:50:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 07 Jun 2021 06:50:09 -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= dMvPxaet5y1S+vPX84QMqXgOECNI3gEyFZRGt6N9Vng=; b=J3sPcZjLG/bmjeLH 8V3C9EJvt4bFDf6ppg7LPKW5llz3qpwqOfyh7yoV0iqSSc7heCL3J85jmoLmYKHF 3VR9O1jo9sRxJ4TroUucbrR4I3qvEed1uFAPhBfTUS2otOh/0kQmUblMKpKfiH0O w9Jc5fvGXLyKXUZ37NZD5o+nJfdXzwVIjU0A5EFBx39dU6KKZ7TuTtzRxlKjmb/B XtUnEeEDzyqaO5T/uufrwYa8+MLTpuPW7yfwN5tnBC9HMVfaN1VrFeBoK6xL1dJT 0L8/H/EOLl4TpfA9GrFQq1cVJ/pfv0gpAAwZrOxC6af2YKyOFsraSJa9YI68oF+x yHqAEQ== 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=dMvPxaet5y1S+vPX84QMqXgOECNI3gEyFZRGt6N9V ng=; b=e4R07jz84IcHBWX/mCWEp2Fu6cSunLcdAJil8mV6GrFRJpmp3JeOy2Tns 2zGq2Su7LFuk6U6ICQXjQY+eiEKAErzee/6i6QIwbRldc2GlCe2xKSRgKu8X2eiq uWUvdOqScirylRLQS9/6knsqh37DpJqo58ZhablowelhmxBieuTbFbLWOcAiNpI8 cZGSQYfny3uSplVuylCs5aM7IrgDuegdy1MZPgFBpD5ApVXG3RTDnc07I7mSty63 lSdAC05Ng4ykWF9EscNtjtQW0oLj87LWCuAYqpKHUIV6M4S1Dx0Pe6Z2ZIErAgRd 7nt4wdcqhFvvZ2sMhczCpIDMApYtA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedtjedgfeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 7 Jun 2021 06:50:08 -0400 (EDT) From: Thomas Monjalon To: Honnappa Nagarahalli Cc: "dev@dpdk.org" , Elena Agostini , nd Date: Mon, 07 Jun 2021 12:50:07 +0200 Message-ID: <6417520.M2XzPVNZdc@thomas> In-Reply-To: References: <20210602203531.2288645-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] gpudev: introduce memory API 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" 06/06/2021 03:10, Honnappa Nagarahalli: > > The new library gpudev is for dealing with GPU from a DPDK application in a > > vendor-agnostic way. > > It would be good to explain how the application using GPU+DPDK would look like. It can be anything to invent. We can give few more words saying it is a computing done in parallel, being either a loop or sequence of tasks. In both cases, the DPDK application running on the CPU must be in control. > Which parts of the workload need DPDK's support? Control: - start task (by function or shared memory variable) - get completion notification (most probably by shared memory) We will add such requirements in v2. > Any requirements on co-existence of GPU with other accelerators? It must be generic to allow any workload with any device. > > As a first step, the features are focused on memory management. > > A function allows to allocate memory inside the GPU, while another one > > allows to use main (CPU) memory from the GPU. > > Is this memory for packet buffers or something else? Can be for packets or for control variables.