From: Xiaozhou Li <xl@CS.Princeton.EDU>
To: dev@dpdk.org
Subject: [dpdk-dev] Performance issues with Mellanox Connectx-3 EN
Date: Wed, 12 Aug 2015 18:20:25 -0500 [thread overview]
Message-ID: <CAL8CsmSoN_0GffBO8h2ivL3cHcKHyE3BMbCpNB_2Mna-uUhZfg@mail.gmail.com> (raw)
Hi folks,
I am getting performance scalability issues with DPDK on Mellanox Connectx-3
.
Each of our machine has 16 cores and a single-port 40G Mellanox Connectx-3
EN. We find out the server throughput *does not scale* with number of
cores. With a single thread on one core, we can get about 2 Mpps with a
simple echo server implementation. However, the performance number does not
increase as we use more cores. Our implementation is based on the l2fwd
example.
I'd greatly appreciate it if anyone could provide some insights on what
might be the problem and how can we improve the performance with
Mellanox Connectx-3
EN. Thanks!
Best,
Xiaozhou
next reply other threads:[~2015-08-12 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 23:20 Xiaozhou Li [this message]
2015-08-13 3:24 ` Xu, Qian Q
2015-08-13 11:13 ` Gilad Berman
2015-08-14 4:10 ` Xiaozhou Li
2015-08-16 6:38 ` Gilad Berman
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=CAL8CsmSoN_0GffBO8h2ivL3cHcKHyE3BMbCpNB_2Mna-uUhZfg@mail.gmail.com \
--to=xl@cs.princeton.edu \
--cc=dev@dpdk.org \
/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).