From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by dpdk.org (Postfix) with ESMTP id E12B5B62 for ; Wed, 16 Sep 2015 10:22:40 +0200 (CEST) Received: by wicfx3 with SMTP id fx3so59086241wic.0 for ; Wed, 16 Sep 2015 01:22:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=8HLXqJibs095DWBZQk4e3j7s/fmDGrtL6aEoEMSE4T0=; b=I1C63IKv3YQ4J55jS0vDrsVH+ESfPVedkhkg/nyyCjcKZC8tSebrUz25xxE1u7Il9t Q0IPIVKQFM6HEX1ztvhGwrhAe0KU5AAqAiZZeKCILV8H0XC6AON3P+nQx3aAWBud7WL7 Y6prN0Qns/hcJAQNbYtCZCAQq28mTj8qR7wPHKy9OEQc2aNFKYjTJI5TExB+Fv0/qP3H YqBG3RdsT2ua04WbjCyaYjP0ppvlrKS1NybTJ4t6mG77NAI2FgJkvSDOcO3TQ7cw49b7 s5VYsSDnp7Z1dynGiFS7ALuKwGRrE9NKFe6a7RilLLKt/XjfbaGYXZqjnQgSGb5U0OkR b3+Q== X-Gm-Message-State: ALoCoQn1dfxpcn/FpXEPt0vLqq8P8ju+SRSeoXlBX3ffvHgp+Mfzmwp6s9Y5cBKv39sZSMNVfRng X-Received: by 10.194.121.202 with SMTP id lm10mr7525806wjb.98.1442391760711; Wed, 16 Sep 2015 01:22:40 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id v6sm25233779wjf.13.2015.09.16.01.22.39 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Sep 2015 01:22:39 -0700 (PDT) From: Thomas Monjalon To: "Xu, Qian Q" Date: Wed, 16 Sep 2015 10:21:32 +0200 Message-ID: <2724688.VL6zfsszk2@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E01DDC0AF@shsmsx102.ccr.corp.intel.com> References: <1439435979-25869-1-git-send-email-qian.q.xu@intel.com> <82F45D86ADE5454A95A89742C8D1410E01DDC0AF@shsmsx102.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2]doc:Add performance test guide about how to get DPDK high perf on Intel platform X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 08:22:41 -0000 Hi, 2015-09-16 02:45, Xu, Qian Q: > Thomas > Could you help check my doc patch, and let me know anything needed fo= r > the merge? I think it would be very helpful for the users to get high= > performance with step-by-step guide. Thx. Yes it is useful. John and Siobhan are the maintainers for the doc. > --- /dev/null > +++ b/doc/guides/perf_test_guide/index.rst Why creating a new guide? Can it be included as a chapter of the Linux user guide? > + Copyright(c) 2010-2015 Intel Corporation. All rights reserved. The dates seem wrong. > +This document is a step-by-step guide about how to get high performa= nce with DPDK on Intel's platform and NICs. OK to focus on Intel platform (must be reflected in the file name), but it should be open to other NICs. It was already commented in previous version: =09http://dpdk.org/ml/archives/dev/2015-August/022704.html > +This document is a step-by-step guide for getting high DPDK performa= nce with Intel's platform and NICs. For other NICs, e.g. Chelsio, Cisco= , Mellanox, the Intel platform/CPU settings could be very similar, but = the specific NIC's configurations may differ from each vendor. Not needed If something is needed for other NICs, other people will add it. > +1. Get an high end Intel=AE NIC, Intel can be removed here. > e.g: Intel=AE XL710. Note: Get an high end NIC means getting a high p= acket rate, since currently 1G and 10G NICs can achieve line rate easil= y, but 40G NIC would be more complicated, so take it as an example.=20 Yes the Intel NIC is an example.