From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: Sepehr Nazary <sepehr.nazary@googlemail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] multi core performance problem
Date: Mon, 4 Jul 2016 22:34:41 +0500 [thread overview]
Message-ID: <CAN7yQ2o0EmPzLkmtjeaDDQQCmjSBwed3VG3VjgKBvg2DF4MSJw@mail.gmail.com> (raw)
In-Reply-To: <CAHtRHyDPhVtW1q9D7N=LgNCV2w26uaK0cv8tD+k1uVZQ=vvSkg@mail.gmail.com>
I am no expert with memory bandwidth and hardware acceleration. But what i
can infer from this issue is that 1 of 2 things
1. Either QPI is being used and the maximum bandwidth is achieved
2. Or RAM has reached it's maximum bandwidth and this is the reason the
higher orders core are getting more bandwidth then lower order
But keith, and Thomas can tell you more on this subject
next prev parent reply other threads:[~2016-07-04 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 10:03 Sepehr Nazary
2016-07-04 17:34 ` Muhammad Zain-ul-Abideen [this message]
2016-07-04 17:40 ` Masoud Moshref Javadi
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=CAN7yQ2o0EmPzLkmtjeaDDQQCmjSBwed3VG3VjgKBvg2DF4MSJw@mail.gmail.com \
--to=zain2294@gmail.com \
--cc=sepehr.nazary@googlemail.com \
--cc=users@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).