From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_ADSP_DISCARD, DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8C96C47096 for ; Thu, 3 Jun 2021 08:57:13 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id E0E9261287 for ; Thu, 3 Jun 2021 08:57:12 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E0E9261287 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=oktetlabs.ru Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 29CF040E78; Thu, 3 Jun 2021 10:57:12 +0200 (CEST) Received: from shelob.oktetlabs.ru (shelob.oktetlabs.ru [91.220.146.113]) by mails.dpdk.org (Postfix) with ESMTP id 2FB4D40DF6 for ; Thu, 3 Jun 2021 10:57:10 +0200 (CEST) Received: from [192.168.38.17] (aros.oktetlabs.ru [192.168.38.17]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by shelob.oktetlabs.ru (Postfix) with ESMTPSA id AF84E7F4E2; Thu, 3 Jun 2021 11:57:09 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 shelob.oktetlabs.ru AF84E7F4E2 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=oktetlabs.ru; s=default; t=1622710629; bh=DOr/HNOIQGoOlXcXj7ek3bL+Oshvbr+BOdMU0Chtyh8=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=WhRRlTa+OUVUbs0kXotY+nu4K/zZyLBkoc6pE+0VCPJzv9iClLrBRF7oKk4O8HC14 SL7VTKlE5ewJTrcKCRUrLKb7SPVHpPCzBcIC/o3C2gS3gK4AopuK/sn3IjRHdXu/EK yQawUphZZHdKzorxAj+EAjDFLDP2kriRMGtS3wok= To: Thomas Monjalon Cc: dev@dpdk.org, Elena Agostini , david.marchand@redhat.com References: <20210602203531.2288645-1-thomas@monjalon.net> <2561723.R1Na977jkj@thomas> <0f3bdf41-ce07-caa4-289a-b05f6727bf0d@oktetlabs.ru> <2734085.Iq8TftFMOa@thomas> From: Andrew Rybchenko Organization: OKTET Labs Message-ID: Date: Thu, 3 Jun 2021 11:57:09 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 In-Reply-To: <2734085.Iq8TftFMOa@thomas> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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" On 6/3/21 11:26 AM, Thomas Monjalon wrote: > 03/06/2021 09:49, Andrew Rybchenko: >> On 6/3/21 10:26 AM, Thomas Monjalon wrote: >>> 03/06/2021 09:06, Andrew Rybchenko: >>>> On 6/2/21 11:35 PM, Thomas Monjalon wrote: >>>>> + * Allocate a chunk of memory on the GPU. >>>> >>>> Looking a below function it is required to clarify here if >>>> the memory is visible or invisible to GPU (or both allowed). >>> >>> This function allocates on the GPU so it is visible by the GPU. >>> I feel I misunderstand your question. >> >> Below function says rte_gpu_malloc_visible() and its >> description highlights that allocated memory is visible to GPU. >> My problem that I don't understand what's the difference >> between these two functions. > > One function allocates in GPU mem, the other allows the GPU to use CPU mem. Ah, I see no. G looks like C and I've not noticed the difference. Now it is clear. My bad.