From: Patrick Robb <probb@iol.unh.edu>
To: Suanming Mou <suanmingm@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>, dev@dpdk.org
Subject: Re: [PATCH] crypto/mlx5: add virtual function device ID
Date: Fri, 1 Mar 2024 11:09:53 -0500 [thread overview]
Message-ID: <CAJvnSUAgSSh9OmmP9_k=6fLhfeLHWPFYpauV+LbGm1-vt+uC2Q@mail.gmail.com> (raw)
In-Reply-To: <20240301123037.1216332-1-suanmingm@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 7:31 AM Suanming Mou <suanmingm@nvidia.com> wrote:
> This adds the virtual function device ID to the list of
> supported NVIDIA devices that run the MLX5 compress PMD.
>
> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> drivers/crypto/mlx5/mlx5_crypto.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/crypto/mlx5/mlx5_crypto.c
> b/drivers/crypto/mlx5/mlx5_crypto.c
> index 4bac723c8b..26bd4087da 100644
> --- a/drivers/crypto/mlx5/mlx5_crypto.c
> +++ b/drivers/crypto/mlx5/mlx5_crypto.c
> @@ -465,6 +465,10 @@ static const struct rte_pci_id
> mlx5_crypto_pci_id_map[] = {
> RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> PCI_DEVICE_ID_MELLANOX_BLUEFIELD3)
> },
> + {
> + RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> + PCI_DEVICE_ID_MELLANOX_CONNECTXVF)
> + },
> {
> .vendor_id = 0
> }
> --
> 2.34.1
>
>
[-- Attachment #2: Type: text/html, Size: 1997 bytes --]
next prev parent reply other threads:[~2024-03-01 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 12:30 Suanming Mou
2024-03-01 16:09 ` Patrick Robb [this message]
2024-03-04 7:24 ` [EXTERNAL] " Akhil Goyal
2024-03-04 7:26 ` Suanming Mou
2024-03-04 9:58 ` Akhil Goyal
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='CAJvnSUAgSSh9OmmP9_k=6fLhfeLHWPFYpauV+LbGm1-vt+uC2Q@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=suanmingm@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).