DPDK patches and discussions
 help / color / mirror / Atom feed
From: Take Ceara <dumitru.ceara@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev]  Performance hit - NICs on different CPU sockets
Date: Mon, 13 Jun 2016 16:07:37 +0200	[thread overview]
Message-ID: <CAKKV4w-FYcK8XLv-HKUBJghNr-Fpsm-_EUqPSCb09zu2aZwxvQ@mail.gmail.com> (raw)

Hi,

I'm reposting here as I didn't get any answers on the dpdk-users mailing list.

We're working on a stateful traffic generator (www.warp17.net) using
DPDK and we would like to control two XL710 NICs (one on each socket)
to maximize CPU usage. It looks that we run into the following
limitation:

http://dpdk.org/doc/guides/linux_gsg/nic_perf_intel_platform.html
section 7.2, point 3

We completely split memory/cpu/NICs across the two sockets. However,
the performance with a single CPU and both NICs on the same socket is
better.
Why do all the NICs have to be on the same socket, is there a
driver/hw limitation?

Thanks,
Dumitru Ceara

             reply	other threads:[~2016-06-13 14:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 14:07 Take Ceara [this message]
2016-06-13 14:28 ` Bruce Richardson
2016-06-14  7:47   ` Take Ceara
2016-06-13 19:35 ` Wiles, Keith
2016-06-14  7:46   ` Take Ceara
2016-06-14 13:47     ` Wiles, Keith
2016-06-16 14:36       ` Take Ceara
2016-06-16 14:58         ` Wiles, Keith
2016-06-16 15:16           ` Take Ceara
2016-06-16 15:29             ` Wiles, Keith
2016-06-16 16:20               ` Take Ceara
2016-06-16 16:56                 ` Wiles, Keith
2016-06-16 16:59                   ` Wiles, Keith
2016-06-16 18:20                     ` Take Ceara
2016-06-16 19:33                       ` Wiles, Keith
2016-06-16 20:00                         ` Take Ceara
2016-06-16 20:16                           ` Wiles, Keith
2016-06-16 20:19                             ` Wiles, Keith
2016-06-16 20:27                               ` Take Ceara

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=CAKKV4w-FYcK8XLv-HKUBJghNr-Fpsm-_EUqPSCb09zu2aZwxvQ@mail.gmail.com \
    --to=dumitru.ceara@gmail.com \
    --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).