DPDK patches and discussions
 help / color / mirror / Atom feed
From: Zachary <zachary.jen@cas-well.com>
To: <dev@dpdk.org>
Cc: "\"Yannic.Chou (周哲正) : 6808\"" <yannic.chou@cas-well.com>,
	"\"Alan Yu (俞亦偉) : 6632\"" <Alan.Yu@cas-well.com>
Subject: [dpdk-dev] DPDK & QPI performance issue in Romley platform.
Date: Mon, 2 Sep 2013 11:22:14 +0800	[thread overview]
Message-ID: <52240466.7050907@cas-well.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]

Hi~

I have a question about DPDK & QPI performance issue in Romley  platform.
Recently, I use DPDK example, l2fwd, to test DPDK's performance in my Romley platform.
When I try to do the test, crossing used CPU, I find the performance dramatically decrease.
Is it true? Or any method can prove the phenomenon?

In my opinion, there should be no this kind of issue here due to QPI have enough bandwidth to deal the kinds of case.
Thus, I am so amaze in our results and can not explain it.
Could someone can help me to solve this problem.

Thank a lot!


My testing environment describe as below:

Platform:         Romley
CPU:                E5-2643 * 2
RAM:               Transcend 8GB PC3-1600 DDR3 * 8
OS:                 Fedora core 14
DPDK:            v1.3.1r2, example/l2fwd
Slot setting:
                      SlotA is controled by CPU1 directly.
                      SlotB is controled by CPU0 directly.

DPDK pre-setting:
a. BIOS setting:
    HT=disable
b. Kernel paramaters
    isolcpus=2,3,6,7
    default_hugepagesz=1024M
    hugepagesz=1024M
    hugepages=16
c. OS setting:
    service avahi-daemon stop
    service NetworkManager stop
    service iptables stop
    service acpid stop
    selinux disable


Example program Command:
a. SlotB(CPU0) -> CPU1
    #>./l2fwd -c 0xc -n 4 -- -q 1 -p 0xc

b. SlotA(CPU1) -> CPU0
    #>./l2fwd -c 0xc0 -n 4 -- -q 1 -p 0xc0

Results:
     use frame size 128 bytes
CPU Affinity

Slot A (CPU1)

Slot B (CPU0)

CPU0

15.9%

96.49%

CPU1

90.88%

24.78%



本信件可能包含瑞祺電通機密資訊,非指定之收件者,請勿使用或揭露本信件內容,並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.

[-- Attachment #2: Type: text/html, Size: 7104 bytes --]

             reply	other threads:[~2013-09-02  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02  3:22 Zachary [this message]
2013-09-02 16:10 ` Stephen Hemminger
2013-09-03 16:19 ` [dpdk-dev] =?gb18030?b?u9i4tKO6IERQREsgJiBRUEkgcGVyZm9ybWFuY2Ug?= =?gb18030?q?issue_in_Romley_platform=2E?=  =?gb18030?B?Qm9iIENoZW4=?=
     [not found] <52289F01.7010503@cas-well.com>
2013-09-06  7:31 ` [dpdk-dev] DPDK & QPI performance issue in Romley platform Zachary

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=52240466.7050907@cas-well.com \
    --to=zachary.jen@cas-well.com \
    --cc=Alan.Yu@cas-well.com \
    --cc=dev@dpdk.org \
    --cc=yannic.chou@cas-well.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).