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 B2A38A0A0F; Fri, 4 Jun 2021 13:09:47 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 38BFC4068F; Fri, 4 Jun 2021 13:09:47 +0200 (CEST) Received: from mail-il1-f172.google.com (mail-il1-f172.google.com [209.85.166.172]) by mails.dpdk.org (Postfix) with ESMTP id 7F97240147 for ; Fri, 4 Jun 2021 13:09:46 +0200 (CEST) Received: by mail-il1-f172.google.com with SMTP id r6so8450159ilj.1 for ; Fri, 04 Jun 2021 04:09:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W51rpozhaayrkF6E8+BhH+MEB6uut+9zkHkKB1+mwwA=; b=rtCHJFWYgKl1xMdMLENybwkQF3fGPV7wjInAAg04Q3XZCtVCTGpticTs6cojXn4Xt9 op5/sQ9+y+QJztIvTOm7+5wUlivrRa0LIge7SIPgze4WPSBTFCYJacpYOfjpDDlYOGbQ v7Y0YwKcjGK6yJSPbrrOX4eSNIP0CTvEUgKhQ3MvCA2Sikgkd4pFEwvtGTvXsYbZHsve RGhEIt/vcA3ycGbgIADXc48+JHLeRgXKuCM8KF+I6QNYnAHdcy6eTHqutz7KrkcPtseF PLxnCouWPwxZ0MkFrstShFLZUMLN2ow9HQyMb+AkN7QsISNQ45M5it+y+pvFE5ix2EXN /aYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W51rpozhaayrkF6E8+BhH+MEB6uut+9zkHkKB1+mwwA=; b=Pg4DLUPOHvlmiTKh3TczCBmjWpZDvBF3gHkUM2UArG3hDmkQk2Rj6N8K691EL/MD+v oAkbzk5xG+8q6QltQvs1ZSwdlxntcEQvU9T15Fvvc4sQ/0bNntvR3BfMiqqKU/x7IeY/ kE4i+aATG961wh6ePQg7OtH9X5xcd/JHYjQ/jLJfKNMMHAkCvtkTGJzLO3lp+YVSWiZL bIJddbGlMM3DnXPGWmBUAbJLA5swpG56N0UPWxofE36tx3SbFG9gEUjeTzpU49YjA2YG 65MlKLmiODWpGs1dfJXHv9O506P06qf5vzXdjD0y5hO7BndYk0brapviz0tcb4CLdqpz xHvg== X-Gm-Message-State: AOAM530IWUn+BHPihPXvIZ4PVXD9fenhoXo5G1MUXOQTVjYqmf75YUiX 9a91A8RkNtGICuiBMrnC+AstMMMFOHBZbLBRr+c= X-Google-Smtp-Source: ABdhPJzSF3muT6HKoCNsKXfZB60walHGOpOxu1Eielz36KVmXojlG3Fv6d9rGG3PWKCAujFKkCLgaV+orjBqpAfRUeM= X-Received: by 2002:a05:6e02:1a6a:: with SMTP id w10mr3566138ilv.130.1622804985744; Fri, 04 Jun 2021 04:09:45 -0700 (PDT) MIME-Version: 1.0 References: <20210602203531.2288645-1-thomas@monjalon.net> <2043513.c5GKn8Mpaa@thomas> In-Reply-To: <2043513.c5GKn8Mpaa@thomas> From: Jerin Jacob Date: Fri, 4 Jun 2021 16:39:29 +0530 Message-ID: To: Thomas Monjalon Cc: Ferruh Yigit , dpdk-dev , Elena Agostini Content-Type: text/plain; charset="UTF-8" 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 Fri, Jun 4, 2021 at 3:58 PM Thomas Monjalon wrote: > > 03/06/2021 11:33, Ferruh Yigit: > > On 6/3/2021 8:47 AM, Jerin Jacob wrote: > > > On Thu, Jun 3, 2021 at 2:05 AM Thomas Monjalon wrote: > > >> + [gpudev] (@ref rte_gpudev.h), > > > > > > Since this device does not have a queue etc? Shouldn't make it a > > > library like mempool with vendor-defined ops? > > > > +1 > > > > Current RFC announces additional memory allocation capabilities, which can suits > > better as extension to existing memory related library instead of a new device > > abstraction library. > > It is not replacing mempool. > It is more at the same level as EAL memory management: > allocate simple buffer, but with the exception it is done > on a specific device, so it requires a device ID. > > The other reason it needs to be a full library is that > it will start a workload on the GPU and get completion notification > so we can integrate the GPU workload in a packet processing pipeline. I might have confused you. My intention is not to make to fit under mempool API. I agree that we need a separate library for this. My objection is only to not call libgpudev and call it libgpu. And have APIs with rte_gpu_ instead of rte_gpu_dev as it not like existing "device libraries" in DPDK and it like other "libraries" in DPDK. > >