From: Thomas Monjalon <thomas@monjalon.net>
To: Elena Agostini <eagostini@nvidia.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4 2/2] gpu/cuda: CPU map GPU memory with GDRCopy
Date: Sun, 27 Feb 2022 17:49:21 +0100 [thread overview]
Message-ID: <5327719.44csPzL39Z@thomas> (raw)
In-Reply-To: <20220225031226.8348-2-eagostini@nvidia.com>
25/02/2022 04:12, eagostini@nvidia.com:
> From: Elena Agostini <eagostini@nvidia.com>
>
> To enable the gpudev rte_gpu_mem_cpu_map feature to expose
> GPU memory to the CPU, the GPU CUDA driver library needs
> the GDRCopy library and driver.
>
> If DPDK is built without GDRCopy, the GPU CUDA driver returns
> error if the is invoked rte_gpu_mem_cpu_map.
>
> All the others GPU CUDA driver functionalities are not affected by
> the absence of GDRCopy, thus this is an optional functionality
> that can be enabled in the GPU CUDA driver.
>
> CUDA driver documentation has been updated accordingly.
>
> Signed-off-by: Elena Agostini <eagostini@nvidia.com>
>
> ----
Should be only 3 dashes to be interpreted by git.
>
> Changelog:
> - Fix checkpatch and doc build issue
> - Added common header to cuda.c and gdrcopy.c
Applied, thanks.
next prev parent reply other threads:[~2022-02-27 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 17:39 [PATCH v1 0/1] gpu/cuda: expose " eagostini
2022-01-11 17:39 ` [PATCH v1 1/1] " eagostini
2022-02-21 22:44 ` [PATCH v2] gpu/cuda: CPU map " eagostini
2022-02-23 19:44 ` [PATCH v3] " eagostini
2022-02-25 3:12 ` [PATCH v4 1/2] doc/gpus: add cuda.ini into features eagostini
2022-02-25 3:12 ` [PATCH v4 2/2] gpu/cuda: CPU map GPU memory with GDRCopy eagostini
2022-02-27 16:49 ` Thomas Monjalon [this message]
2022-02-27 16:48 ` [PATCH v4 1/2] doc/gpus: add cuda.ini into features Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5327719.44csPzL39Z@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=eagostini@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).