From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id CEF2DA034E; Tue, 22 Feb 2022 19:46:49 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A172640DF4; Tue, 22 Feb 2022 19:46:49 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id CB48740042 for <dev@dpdk.org>; Tue, 22 Feb 2022 19:46:47 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 2D59D5C021F; Tue, 22 Feb 2022 13:46:47 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 22 Feb 2022 13:46:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; bh=buYJl2wT/y44/I rLXsBDIgsaKsVtuemOyo49ByNtWaQ=; b=olJQDXNVSV6uJyAn92SgcrMjCayM+t VPKMzkMopZMRjqyuu+a2GqbzzntZb9UUp7m/6F5U4PKOqhAf+ZnNIpQIAJo919UL k3qnZSAlVR5eCW0zOZyZ71GZP0rM7FI8THi6IR9Uc2hWHS8380vAlagAUbcmRuYG FItowLp46GAnwPY8qOx9j6v8iCJCmEdNLVONtUkosXHevFeQum7XpYbaFF80j5Z3 LnEa63mYRrYIs+YIXLxDWdJbP00d0rF1iuSHfgqQeBwzYWTL2u1JwBgGy9rrGr84 CU8EmtaZ12w8S/80mIfcWwwRgtq8Xy0632ZOjHJNXLR2YcBfXtrHKNkA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=buYJl2wT/y44/IrLXsBDIgsaKsVtuemOyo49ByNtW aQ=; b=LQX58mT9xbvC8iAQyKeG2X63quYtCkIQ2zIBRybHXPmnyo8SCVEpC4vFL Bdwh+GgwtMcoKqEaXmfICYinxdPzlU1Th0gak8ZpEFlHWAhIPr3X7sMQvB4IgJIj fnP7JPBhdgR9u+w4KbrNaNn1cbNCmBU3NiFMmxSM+lje0VtUxXKZDmTy4BBf7yZA D/70Yt3+gyZdi33E1zQCFMdhWswB83zR5rSjdSCbYDwGc35JnpyLmlHS+Bexp30h vcE6tXzm2GDnhiMzh4B2uLWxZTVUl/47AffNAmAK7t9uIg+LQcoa3J5tT7v1ML1H ey60PBionOQZpfa3+BgWJUUggcs0g== X-ME-Sender: <xms:li8VYgKJkDpry_DsRCNO5LkcCb4BDFadXhvjd9rswGQ5ui38RdUubA> <xme:li8VYgI-cByv7hd6MNfonaCjOXwFipETGYNz4R6lgtLjXOf1_B__PtDiyq2rWJJIJ 0NafxLCL0ww0MHaFA> X-ME-Received: <xmr:li8VYguLuNBvcT86Uid0btPyq4K5n8gq5-8pCAy0sBpygUzU08MFieIjAe9ylO_R-J1AJ-Bp3b2Kzo5vFJIY-ZPZzA> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrkeekgdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: <xmx:li8VYtaBhqiphNeDZSbZGsxmLs4aKoA4D6wsPs5CTqtZstYYUz6AlQ> <xmx:li8VYnZQdxuT7evVImmVxWsB-ZvczQO0P4CL7xDkIf1ww6BRYn94MQ> <xmx:li8VYpDixeXHjfmobMbDFpqH8WIwombwW6PUAfoRgMbTUy0g7zcMBQ> <xmx:ly8VYoDeCZzpoqlXJOVTWVgHN2JnJFkCQpcRI1oXnkIZgOdardyvLg> Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 22 Feb 2022 13:46:46 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Elena Agostini <eagostini@nvidia.com> Cc: dev@dpdk.org Subject: Re: [PATCH v2] gpudev: use CPU map functionality in comm list Date: Tue, 22 Feb 2022 19:46:44 +0100 Message-ID: <2265539.1SvkZsmPdQ@thomas> In-Reply-To: <20220222002233.21076-1-eagostini@nvidia.com> References: <20220222001703.20604-1-eagostini@nvidia.com> <20220222002233.21076-1-eagostini@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org 22/02/2022 01:22, eagostini@nvidia.com: > From: Elena Agostini <eagostini@nvidia.com> > > rte_gpu_mem_cpu_map() exposes a GPU memory area to the CPU. > In gpudev communication list this is useful to store the > status flag. > > A communication list status flag allocated on GPU memory > and mapped for CPU visibility can be updated by CPU and polled > by a GPU workload. > > The polling operation is more frequent than the CPU update operation. > Having the status flag in GPU memory reduces the GPU workload polling > latency. > > If CPU mapping feature is not enabled, status flag resides in > CPU memory registered so it's visible from the GPU. > > To facilitate the interaction with the status flag, this patch > provides also the set/get functions for it. > > Signed-off-by: Elena Agostini <eagostini@nvidia.com> [...] > * @param ptr > - * Pointer to the GPU memory area to be unmapped. > + * Pointer to the memory area to be unmapped. rebase issue: that reverts another commit sent the same day. I will skip [...] > #endif /* RTE_GPUDEV_H */ > + Will remove lines added at the end of 2 files. Applied, thanks.