DPDK usage discussions
 help / color / mirror / Atom feed
* Re: [dpdk-users] Crypto Framework with QAT Device
@ 2016-08-09 14:07 Trahe, Fiona
  2016-08-09 14:17 ` David Griswold
  0 siblings, 1 reply; 4+ messages in thread
From: Trahe, Fiona @ 2016-08-09 14:07 UTC (permalink / raw)
  To: users, DGriswold; +Cc: Trahe, Fiona

Hi David,

The cryptodev framework can't be used with the earlier QuickAssist devices.(8900-8920)
Even if you got past the differing CSRs the firmware interface is significantly different, so a
complete rewrite of the code which builds the message descriptors would be necessary.
Sorry, that's probably not what you wanted to hear.

A dpdk sample app wrapping the released Intel QuickAssist driver was developed prior to the cryptodev framework:
http://dpdk.org/doc/guides/sample_app_ug/intel_quickassist.html?highlight=quickassist

A better alternative would be to move to one of the newer QuickAssist devices, is that an option?

Regards,
Fiona


Hello,

I'd like to use the crypto framework with an older QAT device from the 8900-8920 (QAT1.5) series.
The current support is for the 8925-8955 series (QAT1.6).
I've installed the ADF software and gotten the crypto framework to recognize the PCIe device,
but the BAR register layout seems to be different from what the framework is expecting when it
goes to create the queue pairs.

Could the experts comment on how difficult this would be and if possible what my next steps might be?

Thanks in advance for your advice,

David

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-users] Crypto Framework with QAT Device
  2016-08-09 14:07 [dpdk-users] Crypto Framework with QAT Device Trahe, Fiona
@ 2016-08-09 14:17 ` David Griswold
  2016-08-09 15:15   ` Trahe, Fiona
  0 siblings, 1 reply; 4+ messages in thread
From: David Griswold @ 2016-08-09 14:17 UTC (permalink / raw)
  To: Trahe, Fiona, users


Thanks Fiona,

Unfortunately, I'm wanting to run on C2xxx (Atom) devices.  I don't believe any of these SKUs have the newer QAT device. Is that correct?
I did get it working with the QAT sample application as you point out.
Just for context, could you explain why the cryptodev framework did not use the ADF driver's API, like the QAT sample uses?
I suspect it had to do with performance but perhaps the API is limiting in some way?

Thanks for your help,

David


From: Trahe, Fiona [mailto:fiona.trahe@intel.com]
Sent: Tuesday, August 09, 2016 10:08 AM
To: users@dpdk.org; David Griswold <DGriswold@advaoptical.com>
Cc: Trahe, Fiona <fiona.trahe@intel.com>
Subject: re: Crypto Framework with QAT Device

Hi David,

The cryptodev framework can't be used with the earlier QuickAssist devices.(8900-8920)
Even if you got past the differing CSRs the firmware interface is significantly different, so a
complete rewrite of the code which builds the message descriptors would be necessary.
Sorry, that's probably not what you wanted to hear.

A dpdk sample app wrapping the released Intel QuickAssist driver was developed prior to the cryptodev framework:
http://dpdk.org/doc/guides/sample_app_ug/intel_quickassist.html?highlight=quickassist

A better alternative would be to move to one of the newer QuickAssist devices, is that an option?

Regards,
Fiona


Hello,

I'd like to use the crypto framework with an older QAT device from the 8900-8920 (QAT1.5) series.
The current support is for the 8925-8955 series (QAT1.6).
I've installed the ADF software and gotten the crypto framework to recognize the PCIe device,
but the BAR register layout seems to be different from what the framework is expecting when it
goes to create the queue pairs.

Could the experts comment on how difficult this would be and if possible what my next steps might be?

Thanks in advance for your advice,

David

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-users] Crypto Framework with QAT Device
  2016-08-09 14:17 ` David Griswold
@ 2016-08-09 15:15   ` Trahe, Fiona
  0 siblings, 0 replies; 4+ messages in thread
From: Trahe, Fiona @ 2016-08-09 15:15 UTC (permalink / raw)
  To: David Griswold, users; +Cc: Trahe, Fiona

Yes, you're correct re the Atom device.

By ADF driver API I assume you mean the QuickAssisst API.
The purpose of the cryptodev framework was to provide a generic API, which could pass crypto requests to SW and HW (QuickAssist and other) devices. The QuickAssist API has a lot of QuickAssist-specific parameters, so was not a good match for this.

As to why the QuickAssist API and user-space driver were not used below the cryptodev layer there are a number of reasons including performance, coding standards, simpler configuration, a desire to take advantage of dpdk features like memory handling, pci device discovery, etc

Fiona




From: David Griswold [mailto:DGriswold@advaoptical.com]
Sent: Tuesday, August 9, 2016 3:18 PM
To: Trahe, Fiona <fiona.trahe@intel.com>; users@dpdk.org
Subject: RE: Crypto Framework with QAT Device


Thanks Fiona,

Unfortunately, I'm wanting to run on C2xxx (Atom) devices.  I don't believe any of these SKUs have the newer QAT device. Is that correct?
I did get it working with the QAT sample application as you point out.
Just for context, could you explain why the cryptodev framework did not use the ADF driver's API, like the QAT sample uses?
I suspect it had to do with performance but perhaps the API is limiting in some way?

Thanks for your help,

David


From: Trahe, Fiona [mailto:fiona.trahe@intel.com]
Sent: Tuesday, August 09, 2016 10:08 AM
To: users@dpdk.org<mailto:users@dpdk.org>; David Griswold <DGriswold@advaoptical.com<mailto:DGriswold@advaoptical.com>>
Cc: Trahe, Fiona <fiona.trahe@intel.com<mailto:fiona.trahe@intel.com>>
Subject: re: Crypto Framework with QAT Device

Hi David,

The cryptodev framework can't be used with the earlier QuickAssist devices.(8900-8920)
Even if you got past the differing CSRs the firmware interface is significantly different, so a
complete rewrite of the code which builds the message descriptors would be necessary.
Sorry, that's probably not what you wanted to hear.

A dpdk sample app wrapping the released Intel QuickAssist driver was developed prior to the cryptodev framework:
http://dpdk.org/doc/guides/sample_app_ug/intel_quickassist.html?highlight=quickassist

A better alternative would be to move to one of the newer QuickAssist devices, is that an option?

Regards,
Fiona


Hello,

I'd like to use the crypto framework with an older QAT device from the 8900-8920 (QAT1.5) series.
The current support is for the 8925-8955 series (QAT1.6).
I've installed the ADF software and gotten the crypto framework to recognize the PCIe device,
but the BAR register layout seems to be different from what the framework is expecting when it
goes to create the queue pairs.

Could the experts comment on how difficult this would be and if possible what my next steps might be?

Thanks in advance for your advice,

David

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [dpdk-users] Crypto Framework with QAT Device
@ 2016-08-04 17:48 David Griswold
  0 siblings, 0 replies; 4+ messages in thread
From: David Griswold @ 2016-08-04 17:48 UTC (permalink / raw)
  To: users

Hello,

I'd like to use the crypto framework with an older QAT device from the 8900-8920 (QAT1.5) series.
The current support is for the 8925-8955 series (QAT1.6).
I've installed the ADF software and gotten the crypto framework to recognize the PCIe device,
but the BAR register layout seems to be different from what the framework is expecting when it
goes to create the queue pairs.

Could the experts comment on how difficult this would be and if possible what my next steps might be?

Thanks in advance for your advice,

David

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2016-08-09 15:15 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-09 14:07 [dpdk-users] Crypto Framework with QAT Device Trahe, Fiona
2016-08-09 14:17 ` David Griswold
2016-08-09 15:15   ` Trahe, Fiona
  -- strict thread matches above, loose matches on Subject: below --
2016-08-04 17:48 David Griswold

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).