From: Elena Agostini <eagostini@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
Cliff Burdick <cburdick@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: [PATCH] gpu: add support for rtx 6000 variant
Date: Thu, 5 Oct 2023 12:50:08 +0000 [thread overview]
Message-ID: <DM6PR12MB4107AC66AA4C52410ED08E2FCDCAA@DM6PR12MB4107.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zL636b-BRqysCFJRPEhWupc+gHgYgxS3TDLZPvc_Wi-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
This patch makes sense to me and actually we should update the drivers/gpu/cuda/devices.h with all the new GPU devices ID
I don’t have an RTX 6000 GPU in my setup so I trust Cliff on the correctness of the ID
Thanks
EA
From: David Marchand <david.marchand@redhat.com>
Date: Friday, 29 September 2023 at 16:56
To: Cliff Burdick <cburdick@nvidia.com>
Cc: dev@dpdk.org <dev@dpdk.org>, Elena Agostini <eagostini@nvidia.com>, NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
Subject: Re: [PATCH] gpu: add support for rtx 6000 variant
External email: Use caution opening links or attachments
Hello,
On Fri, Apr 29, 2022 at 6:53 PM Cliff Burdick <cburdick@nvidia.com> wrote:
>
> Added second GPU PCI device ID for RTX 6000
>
> Signed-off-by: Cliff Burdick <cburdick@nvidia.com>
> ---
> drivers/gpu/cuda/cuda.c | 6 +++++-
> drivers/gpu/cuda/devices.h | 3 ++-
> 2 files changed, 7 insertions(+), 2 deletions(-)
Is this patch still wanted?
It seems it fell through the cracks.
Cc: maintainers.
--
David Marchand
[-- Attachment #2: Type: text/html, Size: 3906 bytes --]
next prev parent reply other threads:[~2023-10-05 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 16:52 Cliff Burdick
2023-09-29 14:55 ` David Marchand
2023-10-05 12:50 ` Elena Agostini [this message]
2023-10-06 7:53 ` David Marchand
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=DM6PR12MB4107AC66AA4C52410ED08E2FCDCAA@DM6PR12MB4107.namprd12.prod.outlook.com \
--to=eagostini@nvidia.com \
--cc=cburdick@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).