From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Shinae Woo <shinae2012@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Performances are not scale with multiple ports
Date: Tue, 28 May 2013 11:22:44 +0200 [thread overview]
Message-ID: <201305281122.44387.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <CA+f=ZztBO=fTqSvj7n8SwKZUNz=fhOq1LcaFMJGJMRhy7xi41w@mail.gmail.com>
Hello,
28/05/2013 04:26, Shinae Woo :
> ./build/l2fwd -cf -n3 -- -p3
> ./build/l2fwd -cf -n3 -- -pf
>
> But both cases, the aggregated performance are not scale.
[..]
> The question is that
> 1. How I can achieve each port receiving full 14.88Mpps ?
> What might be the bottleneck in current environment?
> 2. Why the performance using multiple ports is not scale?
> I guess doubling ports shows the doubling the receiving performance,
> but it shows not. I am curious about what is limiting the packet
> receivng performance.
In order to scale with line-rate performance, you probably have to adjust the
configuration to your hardware. Several parameters should be considered:
- PCIe bus (is it fast enough ?)
- NUMA sockets (copy between NUMA nodes could slow forwarding)
- CPU threads (classic SMP is better than hyperthreading)
To make it short, you could check your PCI bus and your CPU configuration.
For the latter, /proc/cpuinfo should provide enough information with fields
"physical id" and "core id".
--
Thomas
prev parent reply other threads:[~2013-05-28 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 2:26 Shinae Woo
2013-05-28 2:30 ` Naoto MATSUMOTO
2013-05-28 3:05 ` Shinae Woo
2013-05-28 3:15 ` Emre Eraltan
2013-05-28 3:29 ` Stephen Hemminger
2013-05-28 4:00 ` Shinae Woo
2013-05-29 3:09 ` Naoto MATSUMOTO
2013-05-28 9:22 ` Thomas Monjalon [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=201305281122.44387.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=shinae2012@gmail.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).