Hi John,
Thanks for the update.
I have a couple of comments below.
26/11/2018 11:51, John McNamara:
> * **Updated the AESNI MB PMD.**
>
> - The AESNI MB PMD has been updated with additional support for AES-GCM
> - algorithm support.
> -
> -* **Added NXP CAAM JR PMD.**
> -
> - Added the new caam job ring driver for NXP platforms. See the
> - "NXP CAAM JOB RING (caam_jr)" document for more details on this new driver.
> + The AESNI MB PMD has been updated with additional support for the AES-GCM
> + algorithm.
>
> * **Added support for Dynamic Huffman Encoding to Intel QAT comp PMD.**
>
> The Intel QuickAssist (QAT) compression PMD has been updated with support
> for Dynamic Huffman Encoding for the Deflate algorithm.
>
> +* **Added NXP CAAM JR PMD.**
> +
> + Added the new caam job ring driver for NXP platforms. See the
> + "NXP CAAM JOB RING (caam_jr)" document for more details on this new driver.
> +
The CAAM JR is a crypto PMD, so I think it should be listed before
Huffman Encoding, which is a compression PMD.
We could also use the syntax :doc: to refer to its guide.
[...]
> +* ``AVX-512`` support has been disabled for ``GCC`` builds [1] because of a
> + crash [2]. This can affect ``native`` machine type build targets on the
> + platforms that support ``AVX512F`` like ``Intel Skylake`` processors, and
> + can cause a possible performance drop. The immediate workaround is to use
> + ``clang`` compiler on these platforms. The issue has been identified as a
> + GCC defect and reported to the GCC community [3]. Further actions will be
> + taken based on the GCC defect result.
>
> [1]: Commit 8d07c82b239f ("mk: disable gcc AVX512F support")
> [2]: https://bugs.dpdk.org/show_bug.cgi?id=97
The references appear on the same line in HTML. Should we make them a list?
