DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"Ji, Kai" <kai.ji@intel.com>
Subject: RE: [EXT] [PATCH v2] common/qat: enable QAT 2.0c devices
Date: Tue, 19 Sep 2023 12:38:34 +0000	[thread overview]
Message-ID: <CO6PR18MB4484F130AD682E23FF2A138BD8FAA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <DS0PR11MB7631E2DB6159E55A1F21FBC1E6FAA@DS0PR11MB7631.namprd11.prod.outlook.com>

> > Subject: RE: [EXT] [PATCH v2] common/qat: enable QAT 2.0c devices
> >
> >
> > > This commit enables QAT 2.0c devices in the Intel QuickAssist
> > > Technology PMD.
> > > These are 4th Generation QAT, 402xx devices.
> > >
> > > Signed-off-by: Ciara Power <ciara.power@intel.com>
> > >
> > > ---
> > Is it 4944 or 4945? In the code below, the PCI device added is 4945
> 
> The device PF ID is 4944, but the corresponding VF ID used in DPDK for the
> device is 4945.

Applied to dpdk-next-crypto.
Thanks.

      reply	other threads:[~2023-09-19 12:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 12:38 [PATCH] common/qat: enable gen4 c devices Ciara Power
2023-08-11 13:40 ` David Marchand
2023-08-21  9:37   ` Power, Ciara
2023-10-11  7:50     ` David Marchand
2023-08-21  9:33 ` [PATCH v2] common/qat: enable QAT 2.0c devices Ciara Power
2023-09-18 14:31   ` Dooley, Brian
2023-09-19  5:49   ` [EXT] " Akhil Goyal
2023-09-19 11:04     ` Power, Ciara
2023-09-19 12:38       ` Akhil Goyal [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=CO6PR18MB4484F130AD682E23FF2A138BD8FAA@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ciara.power@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.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).