From: "Wiles, Keith" <keith.wiles@intel.com>
To: Take Ceara <dumitru.ceara@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Performance hit - NICs on different CPU sockets
Date: Thu, 16 Jun 2016 15:29:17 +0000 [thread overview]
Message-ID: <BC3153D5-B7BB-465D-BE56-CD872D497268@intel.com> (raw)
In-Reply-To: <CAKKV4w9WTd0sUEHp2XGg9dxXxGPy4A+zd_TNWknS3mq6zNBVPw@mail.gmail.com>
On 6/16/16, 10:16 AM, "Take Ceara" <dumitru.ceara@gmail.com> wrote:
>On Thu, Jun 16, 2016 at 4:58 PM, Wiles, Keith <keith.wiles@intel.com> wrote:
>>
>> From the output below it appears the x710 devices 01:00.[0-3] are on socket 0
>> And the x710 devices 02:00.[0-3] sit on socket 1.
>>
>
>I assume there's a mistake here. The x710 devices on socket 0 are:
>$ lspci | grep -ie "01:.*x710"
>01:00.0 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
>01:00.1 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
>01:00.2 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
>01:00.3 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
>
>and the X710 devices on socket 1 are:
>$ lspci | grep -ie "81:.*x710"
>81:00.0 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
>81:00.1 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
>81:00.2 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
>81:00.3 Ethernet controller: Intel Corporation Ethernet Controller
>X710 for 10GbE SFP+ (rev 01)
Yes, you are correct I miss-read the lspci output.
>
>> This means the ports on 01.00.xx should be handled by socket 0 CPUs and 02:00.xx should be handled by Socket 1. I can not tell if that is the case for you here. The CPUs or lcores from the cpu_layout.py should help understand the layout.
>>
>
>That was the first scenario I tried:
>- assign 16 CPUs from socket 0 to port 0 (01:00.3)
>- assign 16 CPUs from socket 1 to port 1 (81:00.3)
>
>Our performance measurements show then a setup rate of 1.6M sess/s
>which is less then half of what I get when i install both X710 on
>socket 1 and use only 16 CPUs from socket 1 for both ports.
Right now I do not know what the issue is with the system. Could be too many Rx/Tx ring pairs per port and limiting the memory in the NICs, which is why you get better performance when you have 8 core per port. I am not really seeing the whole picture and how DPDK is configured to help more. Sorry.
Maybe seeing the DPDK command line would help.
++Keith
>
>I double checked the cpu layout. We also have our own CLI and warnings
>when using cores that are not on the same socket as the port they're
>assigned too so the mapping should be fine.
>
>Thanks,
>Dumitru
>
next prev parent reply other threads:[~2016-06-16 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 14:07 Take Ceara
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 [this message]
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=BC3153D5-B7BB-465D-BE56-CD872D497268@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=dumitru.ceara@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).