From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH] doc/guides: add info on how to enable QAT
Date: Tue, 30 Aug 2016 16:50:25 +0200
Message-ID: <6602025.TFsYvFOpoj@xps13>
References: <1472563602-111498-1-git-send-email-eoin.breen@intel.com>
 <2225915.7YPDa8br1f@xps13> <1B14A3D5-1244-4B28-94B9-FDB53E9C5052@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Cc: "Breen, Eoin" <eoin.breen@intel.com>, dev@dpdk.org, "Jain,
 Deepak K" <deepak.k.jain@intel.com>, "Trahe, Fiona" <fiona.trahe@intel.com>,
 "Griffin, John" <john.griffin@intel.com>, "Mcnamara,
 John" <john.mcnamara@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54])
 by dpdk.org (Postfix) with ESMTP id C59B03989
 for <dev@dpdk.org>; Tue, 30 Aug 2016 16:50:28 +0200 (CEST)
Received: by mail-wm0-f54.google.com with SMTP id o80so40270963wme.1
 for <dev@dpdk.org>; Tue, 30 Aug 2016 07:50:28 -0700 (PDT)
In-Reply-To: <1B14A3D5-1244-4B28-94B9-FDB53E9C5052@intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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 requ=
ired. The
> >> VF devices exposed by this driver will be used by QAT PMD.
> >>=20
> >> +To enable QAT in DPDK you must change the ./config/common_base fi=
le. Change the
> >> +line 'CONFIG_RTE_LIBRTE_PMD_QAT=3Dn' to 'CONFIG_RTE_LIBRTE_PMD_QA=
T=3Dy' to do this.
> >=20
> > No, the recommended way is to change the value in the generated con=
fig
> > file (.config).
>=20
> The way I have been changing the default configuration options is to =
copy the config/defconfig_XYZ file like defconfig_x86_64-native-linuxap=
p-gcc to a new name say defconfig-x86_64-qat-linuxapp-gcc. Then edit th=
at file and add the CONFIG_RTE_LIBRTE_PMD_QAT=3Dy to the bottom of the =
file. Then =E2=80=98make install T=3Dx86_64-qat-linuxapp-gcc -j=E2=80=99=
.
>=20
> 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 betwe=
en
"make config" and "make" for the documentation.