From: Suanming Mou <suanmingm@nvidia.com>
To: Akhil Goyal <gakhil@marvell.com>, Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH] crypto/mlx5: add virtual function device ID
Date: Mon, 4 Mar 2024 07:26:02 +0000 [thread overview]
Message-ID: <CO6PR12MB539673121E5C810BDFCD090FC1232@CO6PR12MB5396.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484B07DA0BDFBE672F0E44ED8232@CO6PR18MB4484.namprd18.prod.outlook.com>
> -----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
next prev parent reply other threads:[~2024-03-04 7:26 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
2024-03-04 7:24 ` [EXTERNAL] " Akhil Goyal
2024-03-04 7:26 ` Suanming Mou [this message]
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=CO6PR12MB539673121E5C810BDFCD090FC1232@CO6PR12MB5396.namprd12.prod.outlook.com \
--to=suanmingm@nvidia.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=matan@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).