[meta-intel] [PATCH 0/1 daisy/dizzy]: meta-crystalforest:Initial Intel QAT-core Implementation

[Darren Hart]

On 2/26/15 11:26 PM, sundara.rajax.p.manoharan at intel.com wrote:
> From: sundararaja perumal <sundara.rajax.p.manoharan at intel.com>
> 
> Intel's QuickAssist Technology is designed to optimize the use and deployment of
> algorithm accelerators in networking and security applications.
> As the complexity of networking and security applications continues to grow,
> systems need more and more computational resources for workloads,
> including cryptography, data compression, and pattern matching.
> Intel QuickAssist Technology is designed to optimize the use and
> deployment of algorithm accelerators in these kinds of applications.
> 
> Intel QuickAssist Technology employs a hardware-assisted security engine for
> implementing major security functions in both wired and wireless applications.
> This hardware-assisted security engine works to reserve processor cycles
> for application processing, and that in turn not only relieves CPU burden
> but also improves overall system performance.
> 
> Intel QuickAssist Technology, made integral to the Intel architecture,
> aims to address the demand for hardware appliances with built-in
> security processing and to obviate the need for 3rd party co-processors.
> 
> The Intel QuickAssist Technology software consists of an QAT API
> that is implemented by a driver which in turn drives the
> Intel QuickAssist Accelerator hardware.
> The acceleration driver can run in either kernel space or in user space.
> When running in user space, the acceleration driver accesses the
> hardware directly from user space.
> This  Patch enables the QAT core for both Highland forest and
> Crystal forest Platforms.
> 
> The Top-levelpackage name is "QATmux".
> For sub-packages, name is one of the following:
> 1.QAT1.5. for use with Intel Communications Chipset 8900 to 8920 Series.
> 2.QAT1.6. for use with Intel Communications Chipset 8925 to 8955 Series.
> The QATmux can interface to both QAT1.5 and QAT1.6 to bring up DH89xxcc and
> DH895xcc devices.
> 
> The machine specfic  packages are listed below to enable QAT-core.
> QAT-core packages-split contains:
> PACKAGES += "${PN}-dh89xxcc"
> PACKAGES += "${PN}-dh895xcc"
> PACKAGES += "${PN}-app-dh89xxcc"
> PACKAGES += "${PN}-app-dh895xcc"
> PACKAGES += "${PN}-dbg-dh89xxcc"
> PACKAGES += "${PN}-dbg-dh895xcc

-dbg has a specific meaning in yocto and impacts the QA checks and other
packaging routines. I believe these should properly be named:

${PN}-dh89xxcc-dbg

Cc Saul and Paul who I suspect can answer more definitively.



> 
> static binaries are included in single packages-split(FILES_${PN}-staticdev)
> Since we found QA_ISSUE while complie the static-dev package.
> 
> sundararaja perumal (1):
>   meta-crystalforest: Initial Intel QAT recipe
> 
>  .../recipes-extended/qat-core/qat-core.bb          | 367 +++++++++++++++++++++
>  .../qat-core/qat-core/00-qat_core_qa.rules         |   3 +
>  .../0001-Fix-for-QAT_MUX-Compilation-error.patch   |  46 +++
>  .../qat-core/qat-1.6-sample-fix-QA-issue.patch     |  32 ++
>  4 files changed, 448 insertions(+)
>  create mode 100644 meta-crystalforest/recipes-extended/qat-core/qat-core.bb
>  create mode 100644 meta-crystalforest/recipes-extended/qat-core/qat-core/00-qat_core_qa.rules
>  create mode 100644 meta-crystalforest/recipes-extended/qat-core/qat-core/0001-Fix-for-QAT_MUX-Compilation-error.patch
>  create mode 100644 meta-crystalforest/recipes-extended/qat-core/qat-core/qat-1.6-sample-fix-QA-issue.patch
> 

-- 
Darren Hart
Intel Open Source Technology Center