From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] doc: add nic performance guide on linux gsg
Date: Tue, 17 Nov 2015 14:48:33 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023BD8D2@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1447762153-31658-1-git-send-email-qian.q.xu@intel.com>
Hi Qian,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qian Xu
> Sent: Tuesday, November 17, 2015 12:09 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4] doc: add nic performance guide on linux gsg
>
> Add a new guide doc as part of the Linux Getting Started Guide.
>
> The document is a step-by-step guide on how to get high performance with
> DPDK on an Intel platform.
>
> It is designed for users who are not familiar with DPDK but would like to
> get the best performance with NICs.
>
> Signed-off-by: Qian Xu <qian.q.xu@intel.com>
>
> Changes in v4:
> * Update some naming and wordings according to Thomas's comments.
I think the "Changes" should be separated from the commit message by a single line with ---.
Thomas is that correct?
> +Network Interface Card Requirements
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ...
> +
> +Care should be take with NUMA.
> +If you are using 2 or more ports from different NICs, it is best to
> ensure that these NICs on the same CPU socket.
Minor typo: NICs are on the same CPU socket.
> +Example of getting best performance for an Intel NIC
> +----------------------------------------------------
> +
> ..
> +2. Connect the ports to the traffic generator. To check the best
> performance ,we suggest to use high speed traffic generator, such as
> hardware traffic generator IXIA or Spirent. In the sample, we are using
> IXIA.
Thomas suggested previously to omit brand names like IXIA or Spirent. Something generic like the following would be better:
2. Connect the ports to the traffic generator. For high speed testing it is best to use a hardware traffic generator.
This will need to change in the image as well.
> +
> +3. Check the PCI devices numa node (socket id) and get the cores number
> on the exact socket id.
> + In this case, ``82:00.0`` and ``85:00.0`` are both in socket 1, and
> the cores on socket 1 in the referenced platform
> + are 18-35 and 54-71.
> + Note: Don't use one 2 logical cores on the same core (e.g core18 has 2
Minor typo from last time: Don't use 2 logical cores ..
John.
--
prev parent reply other threads:[~2015-11-17 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 12:09 Qian Xu
2015-11-17 14:48 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2023BD8D2@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=qian.q.xu@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).