2016-08-30 13:57, Wiles, Keith: > > 2016-08-30 14:26, Eoin Breen: > >> --- a/doc/guides/cryptodevs/qat.rst > >> +++ b/doc/guides/cryptodevs/qat.rst > >> @@ -78,6 +78,11 @@ Installation > >> To use the DPDK QAT PMD an SRIOV-enabled QAT kernel driver is required. The > >> VF devices exposed by this driver will be used by QAT PMD. > >> > >> +To enable QAT in DPDK you must change the ./config/common_base file. > >> Change the > >> +line 'CONFIG_RTE_LIBRTE_PMD_QAT=n' to 'CONFIG_RTE_LIBRTE_PMD_QAT=y' to do > >> this. > > > > No, the recommended way is to change the value in the generated config > > file (.config). > > The way I have been changing the default configuration options is to copy the > config/defconfig_XYZ file like defconfig_x86_64-native-linuxapp-gcc to a new > name say defconfig-x86_64-qat-linuxapp-gcc. Then edit that file and add the > CONFIG_RTE_LIBRTE_PMD_QAT=y to the bottom of the file. Then ?make install > T=x86_64-qat-linuxapp-gcc -j?. > > Is this not a better way to build a new configuration for a specific reason?
Yes you can also build your own defconfig. I think it is better to stick to simply change the generated file between "make config" and "make" for the documentation.