From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Deepak Kumar Jain <deepak.k.jain@intel.com>
Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com,
Eoin Breen <eoin.breen@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc/guides: add info on how to enable QAT
Date: Tue, 13 Sep 2016 13:50:54 +0200 [thread overview]
Message-ID: <1501529.1jQgDmExi0@xps13> (raw)
In-Reply-To: <1473763630-88760-1-git-send-email-deepak.k.jain@intel.com>
2016-09-13 11:47, Deepak Kumar Jain:
> +#. ``make config T=x86_64-native-linuxapp-gcc``
> +#. Open the ``./build/.config`` file
> +#. Replace ``CONFIG_RTE_LIBRTE_PMD_QAT=n`` with ``CONFIG_RTE_LIBRTE_PMD_QAT=y``
It is better to put commands after "code-block:: console"
Then I suggest this command:
sed -i 's,\(CONFIG_RTE_LIBRTE_PMD_QAT\)=n,\1=y,' build/.config
> +#. ``make``
next prev parent reply other threads:[~2016-09-13 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1472574107-143391-1-git-send-email-eoin.breen@intel.com>
2016-09-13 10:47 ` Deepak Kumar Jain
2016-09-13 11:50 ` Thomas Monjalon [this message]
2016-09-13 13:39 ` Jain, Deepak K
2016-09-13 14:08 ` [dpdk-dev] [PATCH v3] " Deepak Kumar Jain
2016-09-15 14:34 ` Trahe, Fiona
2016-09-17 1:50 ` De Lara Guarch, Pablo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1501529.1jQgDmExi0@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=eoin.breen@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).