diff mbox series

crypto/mlx5: add virtual function device ID

Message ID 20240301123037.1216332-1-suanmingm@nvidia.com (mailing list archive)
State Accepted, archived
Delegated to: akhil goyal
Headers
Series crypto/mlx5: add virtual function device ID |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/Intel-compilation success Compilation OK
ci/intel-Testing success Testing PASS
ci/github-robot: build success github build: passed
ci/intel-Functional success Functional PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-abi-testing success Testing PASS
ci/iol-compile-amd64-testing success Testing PASS
ci/iol-unit-amd64-testing success Testing PASS
ci/iol-unit-arm64-testing success Testing PASS
ci/iol-compile-arm64-testing success Testing PASS
ci/loongarch-compilation success Compilation OK
ci/loongarch-unit-testing success Unit Testing PASS
ci/iol-intel-Performance success Performance Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-broadcom-Functional success Functional Testing PASS
ci/iol-sample-apps-testing success Testing PASS
ci/iol-broadcom-Performance success Performance Testing PASS

Commit Message

Suanming Mou March 1, 2024, 12:30 p.m. UTC 
  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(+)

Comments

Patrick Robb March 1, 2024, 4:09 p.m. UTC | #1 
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
>
>
Akhil Goyal March 4, 2024, 7:24 a.m. UTC | #2 
> Subject: [EXTERNAL] [PATCH] crypto/mlx5: add virtual function device ID
> 
> This adds the virtual function device ID to the list of
> supported NVIDIA devices that run the MLX5 compress PMD.

Compress PMD or crypto 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
Suanming Mou March 4, 2024, 7:26 a.m. UTC | #3 
> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Monday, March 4, 2024 3:24 PM
> To: Suanming Mou <suanmingm@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Cc: dev@dpdk.org
> Subject: RE: [EXTERNAL] [PATCH] crypto/mlx5: add virtual function device ID
> 
> > Subject: [EXTERNAL] [PATCH] crypto/mlx5: add virtual function device
> > ID
> >
> > This adds the virtual function device ID to the list of supported
> > NVIDIA devices that run the MLX5 compress PMD.
> 
> Compress PMD or crypto PMD?

Sorry, it should be crypto.

> 
> >
> > 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
Akhil Goyal March 4, 2024, 9:58 a.m. UTC | #4 
> > Subject: RE: [EXTERNAL] [PATCH] crypto/mlx5: add virtual function device ID
> >
> > > Subject: [EXTERNAL] [PATCH] crypto/mlx5: add virtual function device
> > > ID
> > >
> > > This adds the virtual function device ID to the list of supported
> > > NVIDIA devices that run the MLX5 compress PMD.
> >
> > Compress PMD or crypto PMD?
> 
> Sorry, it should be crypto.
Applied to dpdk-next-crypto with the above change.
Thanks.
diff mbox series

Patch

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
 		}