DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add performance test guide to the linux gsg
Date: Tue, 29 Sep 2015 02:41:09 +0000	[thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E01DE2309@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1584750.6FoDJtCokB@xps13>

Thomas
Thanks for the comments. See my comments inline below. Let me know if you have objections, if no, I will send a v4 patch soon. 

Thanks
Qian

-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] 
Sent: Friday, September 25, 2015 10:11 PM
To: Xu, Qian Q
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] doc: add performance test guide to the linux gsg

2015-09-24 19:48, Qian Xu:
> --- a/doc/guides/linux_gsg/index.rst
> +++ b/doc/guides/linux_gsg/index.rst
> @@ -47,3 +47,4 @@ Contents
>      build_sample_apps
>      enable_func
>      quick_start
> +    perf_test_intel_platform_nic

Why "test"? What about nic_perf_intel_platform?
[Qian] OK. 

> --- /dev/null
> +++ b/doc/guides/linux_gsg/perf_test_intel_platform_nic.rst
[...]
> +Grub Boot Parameters
> +~~~~~~~~~~~~~~~~~~~~
> +
> +The following are some recommendations on GRUB boot settings:
> +
> +#. Use the default grub file as a starting point.
> +
> +#. Reserve 1G huge pages via grub configurations. For example to reserve 8 huge pages of 1G size::
> +
> +      default_hugepagesz=1G hugepagesz=1G hugepages=8
> +
> +#. Isolate CPU cores which will be used for DPDK. For example::
> +
> +      isolcpus=2,3,4,5,6,7,8
> +
> +#. If it wants to use VFIO, use the following additional grub parameters::
> +
> +      iommu=pt intel_iommu=on

These paramters can be set with GRUB, yes.
But they are Linux command line parameters.
I suggest to change the title.
[Qian] OK. 
[...]
> +4. Bind the test ports to igb_uio. For example bind two ports to a DPDK compatible driver and check the status:

Not speaking about VFIO here suggests that igb_uio gives better performance.
By the way, UIO/VFIO is not used by mlx4.
[Qian] In fact not suggests a better performance with igb_uio, but as to VFIO, we need to turn on VT-d in the BIOS, it's an additional step. So here I want to change it as "UIO(e.g: igb_uio) or VFIO(turn on VT-d in the BIOS)", not sure mlx4 uses which module for dpdk running. 
[...]
> +   Note: Don't use one 2 lcores on the same core

one 2 lcores? looks to be a typo
[Qian] Will correct it.
[...]
> +5. As it is known that a XL710 40G port need at least two queue pairs to achieve best performance,

Is it well known? At least it is said here.
[Qian] Maybe well known only in Intel. I will change it as : A XL710 40G port need at least two queue pairs to achieve best performance. 

> +8. Configure the traffic to a traffic generator such as IXIA or Spirent.
> +
> +   * Start creating a stream on packet generator, e.g. IXIA.

Not sure mentioning IXIA or Spirent helps here.
Same comment for the (nice) diagram.
[Qian] *Start creating a stream on packet generator, usually hardware traffic generator can provide line rate traffic, so the NIC's best performance will not be limited by the traffic generator. Hardware traffic generator is like IXIA or Spirent. You can also use high speed software traffic generator to check the NIC's performance. 


Thanks for the documentation effort.

  reply	other threads:[~2015-09-29  2:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 11:48 Qian Xu
2015-09-24 16:25 ` Mcnamara, John
2015-09-25 14:10 ` Thomas Monjalon
2015-09-29  2:41   ` Xu, Qian Q [this message]
2015-09-24 12:37 Mcnamara, John

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=82F45D86ADE5454A95A89742C8D1410E01DE2309@shsmsx102.ccr.corp.intel.com \
    --to=qian.q.xu@intel.com \
    --cc=dev@dpdk.org \
    --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).