From: Thomas Monjalon <thomas@monjalon.net>
To: Elena Agostini <eagostini@nvidia.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4 1/2] doc/gpus: add cuda.ini into features
Date: Sun, 27 Feb 2022 17:48:42 +0100 [thread overview]
Message-ID: <4982089.e9J7NaK4W3@thomas> (raw)
In-Reply-To: <20220225031226.8348-1-eagostini@nvidia.com>
25/02/2022 04:12, eagostini@nvidia.com:
The features list were missed when introducing the driver.
Fixes: 1306a73b1958 ("gpu/cuda: introduce CUDA driver")
Cc: stable@dpdk.org
> Signed-off-by: Elena Agostini <eagostini@nvidia.com>
> ---
> doc/guides/gpus/features/cuda.ini | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
> create mode 100644 doc/guides/gpus/features/cuda.ini
>
> diff --git a/doc/guides/gpus/features/cuda.ini b/doc/guides/gpus/features/cuda.ini
> new file mode 100644
> index 0000000000..eb1aff9a80
> --- /dev/null
> +++ b/doc/guides/gpus/features/cuda.ini
> @@ -0,0 +1,12 @@
> +;
> +; Supported features of the 'cuda' gpu driver.
> +;
> +; Refer to default.ini for the full list of available PMD features.
> +;
> +[Features]
> +Get device info = Y
> +Share CPU memory with device = Y
> +Allocate device memory = Y
> +Free memory = Y
> +CPU map device memory = Y
> +CPU unmap device memory = Y
The last 2 lines will be moved in the next patch implementing the feature.
prev parent reply other threads:[~2022-02-27 16:48 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 GPU memory with GDRCopy 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
2022-02-27 16:48 ` Thomas Monjalon [this message]
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=4982089.e9J7NaK4W3@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).