From: "Qiu, Michael" <michael.qiu@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH]doc: Add performance tuning guide about how to get DPDK high perf on Intel platform.
Date: Mon, 10 Aug 2015 20:37:26 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028604714EEC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8CAC3B@SHSMSX104.ccr.corp.intel.com>
On 2015/8/10 9:11, Zhang, Helin wrote:
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
>> Sent: Monday, August 10, 2015 6:38 AM
>> To: Xu, Qian Q
>> Cc: dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH]doc: Add performance tuning guide about how
>> to get DPDK high perf on Intel platform.
>>
[../..]
>>> +1. For Intel® 40G NICs, special configurations should be set before compiling it,
>> as follows. **Note**: This is very important::
>>> +
>>> + for at least DPDK release 1.8, 2.0 and 2.1, in
>> <dpdk_folder>/config/common_linuxapp
>>> + CONFIG_RTE_PCI_CONFIG=y
>>> + CONFIG_RTE_PCI_EXTENDED_TAG=”on”
>> Please insert it in a i40e doc instead of here. Then you can reference it.
> Good idea!
Yes, agree, actually, for RRC(fm10k), this configure is meaningless.
Thanks,
Michael
> Regards,
> Helin
>
>
next prev parent reply other threads:[~2015-08-10 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 6:34 Qian Xu
2015-08-10 13:37 ` Thomas Monjalon
2015-08-10 16:10 ` Zhang, Helin
2015-08-10 20:37 ` Qiu, Michael [this message]
2015-08-10 16:00 ` Zhang, Helin
2015-08-10 16:01 ` Thomas Monjalon
2015-08-10 16:16 Zhang, Helin
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=533710CFB86FA344BFBF2D6802E6028604714EEC@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=thomas.monjalon@6wind.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).